Re: Inherited Methods and such

[Ray Blaak <rAYblaaK@STRIPCAPStelus.net>]

Maciej Sobczak <see.my.homepage@gmail.com> writes:
> My claim in this lengthy and philosophical discussion is that C++
> provides a complete solution which can be shortly described like this:
> the final type is not established from the very beginning, but is
> progressively moving along the inheritance chain as the subsequent
> constructors of base types complete their work. Thank's to this,
> primitive operations never dispatch further than what can be
> statically reasoned about.

Java has this problem. The rule is to not call overridden functions in the
constructor, since they tend to assume the object is completely constructed.

It is not the type that is the problem. It is calling subclassed methods on an
instance that is not completely constructed yet.

You don't want to progressively change the type either, since that can also
lead to unexpected changes in behaviour.

-- 
Cheers,                                        The Rhythm is around me,
                                               The Rhythm has control.
Ray Blaak                                      The Rhythm is inside me,
rAYblaaK@STRIPCAPStelus.net                    The Rhythm has my soul.