From: Mathieu Fluhr <mfluhr@nero.com>
To: gcc-help@gcc.gnu.org
Subject: g++ 3.4 more restrictive than g++ 3.3 ?
Date: Fri, 15 Jul 2005 12:47:00 -0000 [thread overview]
Message-ID: <1121431610.21076.9.camel@localhost.localdomain> (raw)
Hello all
I'm just wondering about some differences between g++ 3.3 (3.3.6) and
g++ 3.4 (3.4.5). Please have a look to this piece of code:
---8<---------------------------------------------
#include <iostream>
template <class ValueType>
class A
{
protected:
ValueType m_Field;
};
template <class ValueType>
class B : public A<ValueType>
{
void TestParam(ValueType i)
{
m_Field = i;
}
};
int main(void)
{
return 0;
}
---8<---------------------------------------------
As far as I know the C++ language, syntax seems to be correct, and g++
3.3 does not output any error/warning (even with -Wall option). The
problem is that g++ 3.4 (and 4.0 btw) outputs the following:
For g++ 3.4:
Inherit.cpp: In member function `void
B<ValueType>::TestParam(ValueType)':
Inherit.cpp:16: error: `m_Field' undeclared (first use this function)
Inherit.cpp:16: error: (Each undeclared identifier is reported only once
for each function it appears in.)
For g++ 4.0:
Inherit.cpp: In member function 'void
B<ValueType>::TestParam(ValueType)':
Inherit.cpp:16: error: 'm_Field' was not declared in this scope
The very weird thing is that if I change the line 16 from
m_Field = i;
to
this->m_Field = i;
everything works without any kind of problem !!! So is this behaviour
normal ?
Best Regards,
Mathieu Fluhr
next reply other threads:[~2005-07-15 12:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-15 12:47 Mathieu Fluhr [this message]
2005-07-15 13:09 ` Oliver Kullmann
[not found] ` <1121436079.21076.12.camel@localhost.localdomain>
2005-07-15 14:36 ` Oliver Kullmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1121431610.21076.9.camel@localhost.localdomain \
--to=mfluhr@nero.com \
--cc=gcc-help@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).