public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: rdhunt@sandia.gov To: gcc-gnats@gcc.gnu.org Subject: c++/6374: Problem 3560 "Problem with template enum" doesn't seem to be fixed in 3.0.3 Date: Fri, 19 Apr 2002 08:16:00 -0000 [thread overview] Message-ID: <20020419151438.30486.qmail@sources.redhat.com> (raw) >Number: 6374 >Category: c++ >Synopsis: Problem 3560 "Problem with template enum" doesn't seem to be fixed in 3.0.3 >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Fri Apr 19 08:16:01 PDT 2002 >Closed-Date: >Last-Modified: >Originator: Richard Hunt >Release: 3.0.3 >Organization: >Environment: SunOS 5.8 sunru sparc SUNW,Sun-Blade-1000 >Description: I am experiencing the exact problem stated in problem report 3560 which looks like it should have been fixed in Oct. 2001. It was reported in GCC 3.0 so I would think it should have been fixed in 3.0.3. Either way it is still a problem. >How-To-Repeat: g++ main.C -o main main.C:7: invalid use of undefined type `enum Foo<T>::Exceptions' main.C:6: forward declaration of `enum Foo<T>::Exceptions' >Fix: None, but this problem doesn't exist in 2.91 or 2.96 >Release-Note: >Audit-Trail: >Unformatted: ----gnatsweb-attachment---- Content-Type: application/x-unknown-content-type-cfile; name="main.C" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="main.C" CnRlbXBsYXRlIDxjbGFzcyBUPgpjbGFzcyBGb28KewpwdWJsaWM6CiAgZW51bSBFeGNlcHRpb25z IHsgQSxCLEMgfTsKICB2b2lkIGZvbygpIHRocm93KEV4Y2VwdGlvbnMpCiAgICB7CiAgICB9Cn07 CgppbnQgbWFpbigpCnsKICByZXR1cm4gMDsKfQo=
next reply other threads:[~2002-04-19 15:16 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-04-19 8:16 rdhunt [this message] 2002-04-20 7:13 rodrigc
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=20020419151438.30486.qmail@sources.redhat.com \ --to=rdhunt@sandia.gov \ --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).