I have two classes with a parent-child relationship (the Parent
class \"has-a\" Child
class), and the Child
class has a pointer back t
The parent this
pointer, in "pointer terms", is well-defined (otherwise how would the parent constructor know on which instance is it operating?), but:
Child
object aren't initialized yet;So, the parent object in general is still in an inconsistent state; everything the child object will do on construction on the parent object, will be done on a half-constructed object, and this in general isn't a good thing (e.g. if it calls "normal" methods - that rely on the fact that the object is fully constructed - you may get in "impossible" code paths).
Still, if all the child object do with the parent pointer in its constructor is to store it to be use it later (=> when it will be actually constructed), there's nothing wrong with it.
The behaviour is well-defined so long as you don't attempt to dereference the pointer until after the Parent
object has been completely constructed (as @Sergey says in a comment below, if the object being constructed is actually derived from Parent
, then all of its constructors must have completed).
Yes. It's safe to use this
pointer in initialization-list as long as it's not being used to access uninitialized members or virtual functions, directly or indirectly, as the object is not yet fully constructed. The object child
can store the this
pointer of Parent
for later use!