Should relational slots raise an error or a warning if we miss the opposite slot?

[jecisc]

Currently if we miss the opposite slot we are raising an error. The problem is that when this happens because we regenerate a MM, if we close the debugger, the class creation gets interrupted and the image is crashing.

Maybe we should update this behavior to raise a warning and if we proceed the slot will act like a non relational slot? This would prevent to crash the image if a problem occurs when we regenerate a MM?

[badetitou]

Yes, there is something to do with regenerating model.
Should have a way to avoid crashing image

Often it is a question of letting a old model being garbage collected but hard to control this behavior

[jecisc]

I discussed with Marcus and there are two things we can do to improve this.

One should be done short term. The other is more complicated.

First step: A Slot has a special read and write to do actions. Our problems occurs during class migration when migrating the instances. With Marcus we think there should be 2 read/write mechanisms. One for usual usage and one for class migration. Most slot needs to do nothing during class migration except move the content of the slot from the old to the new instance.

Second step: Make ClassBuilder more robust to not crash the image if an error happens. But it's harder to find why this crashes