public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: andrew@andypo.net To: gcc-gnats@gcc.gnu.org Subject: c++/9410: [3.4 regression] inability to access a base classes' member from a templated derived class Date: Wed, 22 Jan 2003 23:06:00 -0000 [thread overview] Message-ID: <20030122230436.13118.qmail@sources.redhat.com> (raw) >Number: 9410 >Category: c++ >Synopsis: [3.4 regression] inability to access a base classes' member from a templated derived class >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: rejects-legal >Submitter-Id: net >Arrival-Date: Wed Jan 22 23:06:00 UTC 2003 >Closed-Date: >Last-Modified: >Originator: Andrew Pollard >Release: gcc-3.4-20030122 >Organization: >Environment: i686-pc-linux-gnu on RedHat8.0/PIII >Description: The following snippet of code no longer compiles. I'm fairly certain it should compile (but I'm not a language laywer). Previous versions of gcc compile it (including gcc-3.4-20030116) hidden.cxx: ----------- struct A { int a; }; template<typename T> struct B : public A { }; template<typename T> struct C : public B<T> { int foo() { return (a); } int bar() { return (this->a); } }; ---------- % g++34 hidden.cxx -c hidden.cxx: In member function `int C<T>::foo()': hidden.cxx:11: error: `a' has not been declared Note how the use with (this->a) works. From a language point of view I would have expected both to work or both to fail. Is this a bug, or just another inability of mine to understand the complexity of templates in C++? >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2003-01-22 23:06 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-01-22 23:06 andrew [this message] 2003-01-23 0:25 bangerth
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=20030122230436.13118.qmail@sources.redhat.com \ --to=andrew@andypo.net \ --cc=gcc-gnats@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: linkBe 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).