public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: boris@kolpackov.net To: gcc-gnats@gcc.gnu.org Cc: boris@isis-server.isis.vanderbilt.edu Subject: c++/10299: parsing error: unqualified type-name from base-class in c-tor's exception specification Date: Wed, 02 Apr 2003 20:16:00 -0000 [thread overview] Message-ID: <20030402192704.6674.qmail@sources.redhat.com> (raw) >Number: 10299 >Category: c++ >Synopsis: parsing error: unqualified type-name from base-class in c-tor's exception specification >Confidential: no >Severity: critical >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Wed Apr 02 20:16:00 UTC 2003 >Closed-Date: >Last-Modified: >Originator: boris@kolpackov.net >Release: g++ (GCC) 3.3 20030331 (prerelease) >Organization: >Environment: linux-i686; ./configure --enable-threads=posix >Description: The code below causes the following output. bash-2.05a$ /usr/local/bin/g++ -Wall ./ExceptionSpecCtor.cpp ExceptionSpecCtor.cpp:13: error: parse error before `)' token ExceptionSpecCtor.cpp:14: error: declaration of `Derived::Derived()' throws different exceptions ExceptionSpecCtor.cpp:9: error: than previous declaration `Derived::Derived() throw (Base::E)' Note that if I comment c-tor out everyhting compiles fine even though foo () member functions uses semantically the same construct. -------------------------------------- struct Base { class E {}; }; struct Derived : public virtual Base { Derived () throw (E); void foo () throw (E); }; Derived::Derived () throw (E) { } void Derived::foo () throw (E) { } >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2003-04-02 20:16 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-04-02 20:16 boris [this message] 2003-04-02 22:40 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=20030402192704.6674.qmail@sources.redhat.com \ --to=boris@kolpackov.net \ --cc=boris@isis-server.isis.vanderbilt.edu \ --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).