public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/9558: subclass cannot find parent members without explicit "this->" in some cases Date: Tue, 04 Feb 2003 02:46:00 -0000 [thread overview] Message-ID: <20030204024600.3883.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/9558; it has been noted by GNATS. From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: "Ryan C. Gordon" <ryan@epicgames.com> Cc: gcc-bugs@gcc.gnu.org, <gcc-gnats@gcc.gnu.org>, <mark@codesourcery.com> Subject: Re: c++/9558: subclass cannot find parent members without explicit "this->" in some cases Date: Mon, 3 Feb 2003 20:43:26 -0600 (CST) > After thinking about it, (and based on the initial response of "can we > add this as a FAQ to non-bugs"), ...which I just took care of... > perhaps the problem is in the error > message more than the behaviour. My assumption was this was a problem in > the new parser and that it wasn't resolving because something had > confused it. Is there a way to differentiate between this and a variable > that absolutely positively does not exist, and issue a different error > message? I think that would at least stop more incorrect bug reports on > the issue. It's hard to come up with something reasonable, because of cases like template <typename T> struct A { int i; }; template <typename T> struct B : A<T> { int f() {return i;} }; template <> struct A<int> { }; // oops In B::f, what is the compiler supposed to tell you? I guess one would like to have something like Error: "i" undeclared (did you mean "this->i" or A<T>::i"?) The gotcha comes in the specialization of A<int>: there really is no "i" in this class. There are worse cases, like template <typename T> struct B : typename A<T>::some_typedef {...}; where you really have no idea what the base class might be, unless you actually instantiate it. Of course, this doesn't mean that Mark or someone else has ingeneous ideas for warnings... W. ------------------------------------------------------------------------- Wolfgang Bangerth email: bangerth@ticam.utexas.edu www: http://www.ticam.utexas.edu/~bangerth/
next reply other threads:[~2003-02-04 2:46 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-02-04 2:46 Wolfgang Bangerth [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-02-04 2:36 Ryan C. Gordon 2003-02-04 0:56 Wolfgang Bangerth 2003-02-04 0:26 Wolfgang Bangerth 2003-02-03 23:45 bangerth 2003-02-03 23:36 ryan
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=20030204024600.3883.qmail@sources.redhat.com \ --to=bangerth@ticam.utexas.edu \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).