MaClassDefinition in question

[Chris Muller]

Hi Hilaire, sorry for the delayed response; I have just returned from a holiday.

Instances of MaClassDefinition are kept for each version of each class
that was ever committed to the repository.

When a ReadStrategy is specified, it should work fine for the old and
new versions of the classes.  See
MaReadStrategy>>#convertSpecificationsToIdsUsing: to see that it does
indeed create depth-specifications for every known version of the
class.  The variable that does not exist in the old version will
simply

There is no need to "remove" the instance of your domain as it evolves
with your class model; the new variables will have nil just like
Smalltalk until you populate them and commit.

Can you try again to explain the exact problem you are having?
Perhaps a script that reproduces it would improve our mutual clarity?

Regards,
  Chris

On 7/20/07, Hilaire Fernandes <hilaire at ofset.org> wrote:
> I have found that a MaClassDefinition instance for one of my domain class
> still refers to an old definition.
>
> I discover this when updating a readstrategy with an instance variable in
> the newest class definition but not in the older one (and not in the one
> defined by the MaClassDefinition instance)
>
> I try to remove the instances of my domain. Close and restart the session.
> But still I got the oldest definition and obviously the readstrategy
> definition is causing error.
>
> Hilaire
>
> _______________________________________________
> Magma mailing list
> Magma at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/mailman/listinfo/magma
>