lets say to got a computer object.. then you matbe could add a new keyboard with a lot of new shortcuts but without changing something to the computer.. in other words you will never ovveride anything.. you just extend..

For it basicly can’t override anything it basicly creates a different new interface to interact with the object where it also is able to get to the protected members, it is basicly a wrapper :p.

Have you thought about downcasting objects where the downcast actually has more properties? I realize that this might be slightly difficult and would probably require specific invariants to keep it all going.

To illustrate, you would have a object of say type fish. which just has basic properties and methods of a fish. Now you could downcast (upgrade it? maybe we should call it ‘evolve’) it to a cod fish where all sorts of extra properties and methods are defined. The codfish object would be initialised with the fish object.

Maybe it is better illustrated with shapes. Say you have a object of type ‘shape’ which is a high abstract type object. Now you really need a cube, could you ‘evolve’ the shape into a ‘cube’. Depending on the properties of the shape, the answer might be yes or no. Or you might have to change the shape in order to ‘evolve’ it into a cube.

edited post… guess i was to vague

Also the way it would be implemented would be totaly different.. more like a wrapper instead of its own instance i guess