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++/7761: gcc reports internal error code 383 on invalid namespace usage. Date: Thu, 29 Aug 2002 11:16:00 -0000 [thread overview] Message-ID: <20020829161600.31853.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/7761; it has been noted by GNATS. From: Gabriel Dos Reis <gdr@integrable-solutions.net> To: pgoverea@akamai.com Cc: gcc-gnats@gcc.gnu.org Subject: Re: c++/7761: gcc reports internal error code 383 on invalid namespace usage. Date: 29 Aug 2002 18:08:22 +0200 pgoverea@akamai.com writes: | compile file containing: | struct A { }; | namespace A { struct B {}; } | using A::B; Recent versions of GCC no longer craches but the compiler is clearly bogus since it should have rejected the namespace declaration definition. I bet this behaviour is due to the fact that the front-end source was copied from C and it wasn't updated to take into account C++'s more stringent rules about names. -- Gaby
next reply other threads:[~2002-08-29 16:16 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-08-29 11:16 Gabriel Dos Reis [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-10-31 13:33 bangerth 2002-09-13 13:54 nathan 2002-09-13 13:53 nathan 2002-08-29 9:16 pgoverea
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=20020829161600.31853.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).