Are you moving over to Bmax, (and do you think decapsulate is a real word)?
i definitely will be... hopefully sooner than later... got a few issues to deal with before i start spending computer funds again though... the least being the judge's decisions on equitable distribution... and my avoiding any possible suggestion of dissipation of assets...
in short, as soon as i can, or when the 3D module comes out... whichever is first :)
Now maybe this seems contrary to the whole purpose of encapsulating the properties of a TYPE or CLASS, but the List IS a property of the Type, so it also needs to be within the definition. Not to put it in the type, would infact decapsulate the type.
from what i'm reading, i would be compelled to disagree here... i would maintain the LIST externally, it does not appear to be a property of the TYPE if it is accessable and changeable outside the TYPE definition...
the TYPE should contain a separate field that can be associated with the LIST, or can obtain values from the list... but the LIST itself looks like it should be its own independent entity.
again... not being that intimate with BMax coding, i may be missing something here...
** added **
after thinking about this again, i now don't even see the need for a LIST at all... could you tell me what is the purpose or function of the LIST...
--Mike