[EMAIL PROTECTED] wrote: > (When you extend an existing class, it actually creates > +a new class, that replaces the old class in the Namespace, but the old > +class can't be thrown away if it has objects instantiated in it. The old > +objects still point to the old class and do their method resolution and > +attribute lookup through that class. If a class hasn't been > +instantiated, adding a method doesn't create a new class. If it has been > +instantiated, the it creates a new class the first time its extended, > +and then doesn't create a new class until it is instantiated again.)
Is it intended that if languages need to make changes to the behaviour of existing obejcts through their type, that something may follow up after this and replace the old objects with objects of the new type? Sam.
