public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Neil Booth <neil@daikokuya.demon.co.uk> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c++/6601: [parser] Parse error when using :: qualified name in template Date: Thu, 16 May 2002 13:06:00 -0000 [thread overview] Message-ID: <20020516200602.4483.qmail@sources.redhat.com> (raw) The following reply was made to PR c++/6601; it has been noted by GNATS. From: Neil Booth <neil@daikokuya.demon.co.uk> To: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at> Cc: Wolfgang Bangerth <bangerth@math.ethz.ch>, Reiner Hauser <rhauser@fnal.gov>, gcc-gnats@gcc.gnu.org, lerdsuwa@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-patches@gcc.gnu.org Subject: Re: c++/6601: [parser] Parse error when using :: qualified name in template Date: Thu, 16 May 2002 21:00:51 +0100 Gerald Pfeifer wrote:- > On Thu, 16 May 2002, Wolfgang Bangerth wrote: > >> Maybe this can go into that 'bugs which aren't really bugs' web page you > >> got ? It might give people a clue when they run into similar problems. > > If we don't have digraphs disabled by default, that'd be something I'd > consider changing. I disagree - they're part of the language, and we've now released 3.0 and 3.1 with them enabled by default (and they are in 2.96 too I believe). So there seems little point reverting now - most code will have already been fixed. Neil.
next reply other threads:[~2002-05-16 20:06 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-05-16 13:06 Neil Booth [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-05-17 14:26 Jason Merrill 2002-05-16 14:26 John Marshall 2002-05-16 13:56 Gabriel Dos Reis 2002-05-16 13:26 Nathan Sidwell 2002-05-16 11:56 Gerald Pfeifer 2002-05-16 1:06 Wolfgang Bangerth 2002-05-14 8:36 Reiner Hauser 2002-05-14 7:36 Wolfgang Bangerth 2002-05-14 7:00 lerdsuwa
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=20020516200602.4483.qmail@sources.redhat.com \ --to=neil@daikokuya.demon.co.uk \ --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).