Inherited members from templated class

[Xavier Décoret]

I have just come across the following fact.

Names defined in a template superclass of the current template must be
qualified as being from the superclass. Alternatively, you can also
qualify those names by preceding them with this->. An example might be
clearer to read:
template <typename T> struct Base
{
int m;
};

template <typename T> struct Derived : public Base<T>
{
void g()
{
m++; // ERROR: Name not found.

this->m++; // OK
Derived::m++; // OK
Base<T>::m++; // OK
}
};
This appears when migrating from gcc3 to gcc4 (see
http://developer.apple.com/releaseno...tingToGCC.html)
..

My question is: is that conform to the standard (sorry to ask, but I am
not familiar with reading through the standard. This might be trivial to
answer for those who are.)

[novice]

Please tell me where i can get free e-book
" Professional C++" wrox series

[Ian Collins]

novice wrote:

Please tell me where i can get free e-book
" Professional C++" wrox series

What makes you think it's free? Just buy it.

--
Ian Collins.

[Fei Liu]

Xavier Décoret wrote:

I have just come across the following fact.

Names defined in a template superclass of the current template must be
qualified as being from the superclass. Alternatively, you can also
qualify those names by preceding them with this->. An example might be
clearer to read:
template <typename T> struct Base
{
int m;
};

template <typename T> struct Derived : public Base<T>
{
void g()
{
m++; // ERROR: Name not found. This doesn't seem right. struct members are implicitly declared public
by default thus accessible in derived class. Post your complete code
please.
this->m++; // OK
Derived::m++; // OK
Base<T>::m++; // OK
}
};
This appears when migrating from gcc3 to gcc4 (see
http://developer.apple.com/releaseno...tingToGCC.html)
.

My question is: is that conform to the standard (sorry to ask, but I am
not familiar with reading through the standard. This might be trivial to
answer for those who are.)

[Victor Bazarov]

Fei Liu wrote:

Xavier Décoret wrote:

I have just come across the following fact.

Names defined in a template superclass of the current template must be
qualified as being from the superclass. Alternatively, you can also
qualify those names by preceding them with this->. An example might be
clearer to read:
template <typename T> struct Base
{
int m;
};

template <typename T> struct Derived : public Base<T>
{
void g()
{
m++; // ERROR: Name not found.
This doesn't seem right. struct members are implicitly declared public
by default thus accessible in derived class. Post your complete code
please.

Read about "dependent names" in the FAQ.

this->m++; // OK
Derived::m++; // OK
Base<T>::m++; // OK
}
};
This appears when migrating from gcc3 to gcc4 (see
http://developer.apple.com/releaseno...tingToGCC.html)
.

My question is: is that conform to the standard (sorry to ask, but I am
not familiar with reading through the standard. This might be trivial to
answer for those who are.)

Xavier:

Yes, it conforms.

V
--
Please remove capital As from my address when replying by mail