public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bangerth@dealii.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	meinlschmidt@informatik.uni-erlangen.de, nobody@gcc.gnu.org
Subject: Re: c++/10682: [3.3/3.4 regression] chokes on a typedef for an enum inside a class template
Date: Thu, 08 May 2003 15:43:00 -0000	[thread overview]
Message-ID: <20030508154304.10652.qmail@sources.redhat.com> (raw)

Old Synopsis: gcc 3.3 chokes on a typedef for an enum, both inside a class template
New Synopsis: [3.3/3.4 regression] chokes on a typedef for an enum inside a class template

State-Changed-From-To: open->analyzed
State-Changed-By: bangerth
State-Changed-When: Thu May  8 15:43:03 2003
State-Changed-Why:
    Confirmed, a regression from 3.2:
    -------------------------------
    template<typename T>
    struct Foo {
      enum E {a,b,c};
      typedef E EE;
    };
    
    void baz(Foo<int>::EE x);
    --------------------------
    
    g/x> /home/bangerth/bin/gcc-3.2.3-pre/bin/c++ -c z.cc
    
    g/x> /home/bangerth/bin/gcc-3.3-pre/bin/c++ -c z.cc
    z.cc:7: error: `EE' is not a member of type `Foo<int>'
    z.cc:7: error: parse error before `)' token
    
    g/x> /home/bangerth/bin/gcc-3.4-pre/bin/c++ -c z.cc
    z.cc:7: error: variable or field `baz' declared void
    z.cc:7: error: `EE' is not a member of `struct Foo<int>'
    
    The whole thing works if we do
        typedef int EE;
    instead, so this is really a bug.
    
    W.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10682


             reply	other threads:[~2003-05-08 15:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-08 15:43 bangerth [this message]
2003-05-20 17:14 jason
2003-05-20 21:21 jason

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=20030508154304.10652.qmail@sources.redhat.com \
    --to=bangerth@dealii.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=meinlschmidt@informatik.uni-erlangen.de \
    --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: 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).