views:

93

answers:

5

Hi everyone.

I'd like to create a class that is associated to another class in some sort of parent-child relationship. For this the "child" class needs a reference to it's parent.

For example:

template <typename T>
class TEvent {
    private: T* Owner;
    public: TEvent(T* parent) : Owner(parent) {}
};

class Foo {
    private: TEvent<Foo> Froozle; // see below
};

Now the problem is that I can't initialize the Froozle instance directly, nor using the instanciation list of Foo's constructor, because this references are not allowed there. Apart from adding another method setParent(T*) (which I don't like too much because it means that I have to leave the TEvent<> instance in an invalid state), is there a way to achieve this?

+6  A: 

It is OK to use this in the initialization list, as long as it is not used to access any members that may not have been initialized yet.

Space_C0wb0y
What he says. As long as the objects you pass `this` to "know" not to touch it during their construction (because the object `this` refers to isn't fully constructed at that moment), doing so is fine, even though some compilers (notably VC) emit a warning for it.
sbi
VC++ is the key point here. It works indeed. Seems like I have to suppress that "error" forcibly. Thanks alot!
Markus
+1  A: 

This is supposed to work; in fact,

template<class T>
class Child {
private:
    T *parent;
public:
    Child(T *parent) : parent(parent) {}
};
class Parent {
private:
    Child<Parent> child;
public:
    Parent() : child(this) {}
};

compiles fine for me with both g++ 4.4.5 and clang++ 2.8.

What is failing for you?

ephemient
The 'treat warnings as errors' compiler flag of VC and the MSDN documentation header that says "Error Message". :) You're absolutely right - It works, I just didn't see it. Thanks alot!
Markus
+1  A: 

From the standard 12.6.2/7 "Initializing bases and members" (emphasis mine):

Names in the expression-list of a mem-initializer are evaluated in the scope of the constructor for which the mem-initializer is specified.

[Example:

class X {
    int a;
    int b;
    int i;
    int j;

public:
    const int& r;
    X(int i): r(a), b(i), i(i), j(this->i) {}
};

initializes X::r to refer to X::a, initializes X::b with the value of the constructor parameter i, initializes X::i with the value of the constructor parameter i, and initializes X::j with the value of X::i; this takes place each time an object of class X is created. ]

[Note: because the mem-initializer are evaluated in the scope of the constructor, the this pointer can be used in the expression-list of a mem-initializer to refer to the object being initialized. ]

Michael Burr
That looks crazy. :D
Markus
+1  A: 

If you're looking to suppress the warning, just do this:

class Foo
{
public:
    Foo() :
    Froozle(get_this())
    {}

private:
    Foo* get_this()
    {
        return this;
    }

    TEvent<Foo> Froozle; // see below
};

The indirection is enough to stop it.

GMan
Heh. Why is a method call okay but a direct reference not? Silly compiler :)
ephemient
A: 

I don't think it's failing on you, unless you have the warning level set to 4 (or similar, I assume Visual Studio) and have enabled "treat warnings as errors".

Basically, this warning is A Good Thing, since it won't let you accidentally use the this pointer when what it points at is yet to be constructed.

However, when you know what you are doing wherever this is passed in the initialization list, the warning and error caused by this will be annoying.

You can get rid of it (again, assuming Visual Studio) by decorating the constructor (unless it's defined in the class declaration - then you must decorate all the class):

// warning C4355: 'this' : used in base member initializer list
#pragma warning (push)
#pragma warning (disable : 4355)
some_class::some_class()
: ...
{
}
#pragma warning (pop)
Johann Gerell