public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Gabriel Dos Reis <gdr@integrable-solutions.net> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/10497: Bug #909 not closed : Spurious error using nested classes in constructor calls Date: Fri, 25 Apr 2003 13:46:00 -0000 [thread overview] Message-ID: <20030425134601.20559.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/10497; it has been noted by GNATS. From: Gabriel Dos Reis <gdr@integrable-solutions.net> To: have@ann.jussieu.fr Cc: gcc-gnats@gcc.gnu.org Subject: Re: c++/10497: Bug #909 not closed : Spurious error using nested classes in constructor calls Date: 25 Apr 2003 15:29:46 +0200 have@ann.jussieu.fr writes: | >Number: 10497 | >Category: c++ | >Synopsis: Bug #909 not closed : Spurious error using nested classes in constructor calls | >Confidential: no | >Severity: serious | >Priority: medium | >Responsible: unassigned | >State: open | >Class: sw-bug | >Submitter-Id: net | >Arrival-Date: Fri Apr 25 13:26:00 UTC 2003 | >Closed-Date: | >Last-Modified: | >Originator: have@ann.jussieu.fr | >Release: 2.95, 3.0, 3.2, 3.3 | >Organization: | >Environment: | Linux | >Description: | Bug #909 does not seem to be fixed even if it is closed. | With g++ > 3.0, the error becomes: | " error: type specifier omitted for parameter `Z' " Did you try mainline a.k.a GCC-3.4 (experimental)? I think this is a problem with the old parser which is trying to parse this | A a(A::Nested(i), Z); // ERROR: type specifier omitted for parameter as a function declaration and chocks by the time it encounters 'Z'. | A e(A::Nested(i)); // OK the old parser can correctly parse 'e' as a declaration of a function taking an 'A::Nested' and returning an 'A'. -- Gaby
next reply other threads:[~2003-04-25 13:46 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-04-25 13:46 Gabriel Dos Reis [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-04-25 15:06 bangerth 2003-04-25 13:36 Andrew Pinski 2003-04-25 13:26 have
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=20030425134601.20559.qmail@sources.redhat.com \ --to=gdr@integrable-solutions.net \ --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).