On Tue, 2003-05-13 at 13:45, Luke Opperman wrote:
> could you quickly explain the purpose behind having SoCol and Col
> classes in Col.py? For now, just curious what the mechanism for
> creating new Columns should be, do I need one of each?
SOCol objects (and subclasses) cannot be shared between classes,
including between a class and its subclass. But, specifically for
subclasses, *something* has to be shared, because inherited columns will
use the same object to specify the column as the superclass uses. So
Col (and subclasses) exist as a sort of placeholder, which get turned
into a SOCol object for each class instance.
So yes, you need one of each. The non-SO* classes all look pretty much