on 8/02/02 3:02 PM, Henrik Gedenryd at h.gedenryd at open.ac.uk wrote:

> ducasse wrote:
> 
>> Now it came to me that the problem is easily solved by proposing a kind of
>> protocol (like in the loaded in envy or the post load action in VW) so that
>> we can specify action to be performed when a module is loaded.
> 
> There is already such a protocol, look in the category of Class>>initialize.
> 
>> Note that this solution does not say anything about the semantics of the
>> deltamodule. So henrik are the method in delat modules (class extentions)
>> able to mask an existing method (in Envy this is impossible, in VW it is).
> 
> Yes.
> 
>> Then can I with a delta module override the class definition. I hope not.
> 
> Yes here too, but it isn't implemented yet.
> 
> Principle: anything that could be changed between to versions of a module
> should be doable by a DeltaModule. Then you use it responsibly :-)

Yes but I would not allow class redefinition. Because you may end up to have
to recompile the complete class and hierarchy just because a deltamodule
changes the class definition.

So the fact that we can do it is not the proof that we should ;)