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++/3907: nested template parm collides with member name Date: Thu, 21 Nov 2002 18:47:00 -0000 [thread overview] Message-ID: <20021116013601.18691.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/3907; it has been noted by GNATS. From: Wolfgang Bangerth <bangerth@ticam.utexas.edu> To: gcc-bugs@gcc.gnu.org, <gcc-gnats@gcc.gnu.org> Cc: Subject: Re: c++/3907: nested template parm collides with member name Date: Fri, 15 Nov 2002 19:32:58 -0600 (CST) The original testcase was a rejection of illegal code (because it accessed the nonexisting inner type U::S), but I can make this a rejects-legal this way: ----------------------------------------- template <int N> struct T { enum E { }; }; template <int s> struct U {}; template <int s> struct C { template <int t> struct S : U<t> {}; typename T<s>::E t; }; ----------------------------- tmp/g> /home/bangerth/bin/gcc-3.3x-pre/bin/c++ -c x.cc x.cc:6: error: declaration of `typename T<N>::E C<s>::t' x.cc:5: error: changes meaning of `t' from `int t' Of course, the scope of the template arg "t" should be limited to the end of the template class declaration. If someone is adventurous: the initial code accepted invalid code. I played with this further, and it is now PR 8596. Regards Wolfgang ------------------------------------------------------------------------- Wolfgang Bangerth email: bangerth@ticam.utexas.edu www: http://www.ticam.utexas.edu/~bangerth
next reply other threads:[~2002-11-16 1:36 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-11-21 18:47 Wolfgang Bangerth [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-08-01 3:02 nathan
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=20021116013601.18691.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).