public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/23586] [3.4/4.0/4.1 regression] Bad diagnostic for invalid namespace-name Date: Tue, 30 Aug 2005 16:23:00 -0000 [thread overview] Message-ID: <20050830162238.852.qmail@sourceware.org> (raw) In-Reply-To: <20050826221750.23586.reichelt@gcc.gnu.org> ------- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-08-30 16:22 ------- Subject: Bug 23586 CVSROOT: /cvs/gcc Module name: gcc Changes by: reichelt@gcc.gnu.org 2005-08-30 16:22:01 Modified files: gcc/cp : ChangeLog parser.c name-lookup.c Log message: PR c++/23586 * parser.c (cp_parser_namespace_name): Move diagnostic for invalid namespace-name to here from ... * name-lookup.c (do_namespace_alias): ... here and ... (do_using_directive): ... here. Remove dead code. Patches: http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/cp/ChangeLog.diff?cvsroot=gcc&r1=1.4862&r2=1.4863 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/cp/parser.c.diff?cvsroot=gcc&r1=1.351&r2=1.352 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/cp/name-lookup.c.diff?cvsroot=gcc&r1=1.138&r2=1.139 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23586
next prev parent reply other threads:[~2005-08-30 16:22 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-08-26 22:20 [Bug c++/23586] New: " reichelt at gcc dot gnu dot org 2005-08-26 22:21 ` [Bug c++/23586] " pinskia at gcc dot gnu dot org 2005-08-26 22:37 ` reichelt at gcc dot gnu dot org 2005-08-30 16:23 ` cvs-commit at gcc dot gnu dot org [this message] 2005-08-30 16:28 ` cvs-commit at gcc dot gnu dot org 2005-08-30 16:43 ` [Bug c++/23586] [3.4 " reichelt at gcc dot gnu dot org 2005-08-31 8:47 ` reichelt at gcc dot gnu dot org 2005-08-31 10:16 ` cvs-commit at gcc dot gnu dot org 2005-08-31 10:17 ` reichelt at gcc dot gnu dot org
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=20050830162238.852.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).