Ram�n Jim�nez wrote: > it seems to be this pattern happens in Daniel's system > more than once (i.e. it's not only limited to "processes"). > So abstract classes could be used as superclasses for specific > instances of the problem... At least, that's what I understood.
Okay. The part that can be made abstract is the pointer to the "parent", the transient parent oref, an the parentOpen() method. But the implementation I proposed works on a per property basis. The calculated property plus override persistent property can't be done in abstraction. [If a datatype could implement a "hidden" private property, and make itself actually a calculated property, that would help a lot!]
