public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: neil@gcc.gnu.org
To: ballan@c425089-a.plstn1.sfba.home.com, gcc-bugs@gcc.gnu.org,
	gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org
Subject: Re: c++/4190: digraph interference in class names
Date: Sat, 01 Sep 2001 02:15:00 -0000	[thread overview]
Message-ID: <20010901091518.29952.qmail@sourceware.cygnus.com> (raw)

Synopsis: digraph interference in class names

State-Changed-From-To: open->closed
State-Changed-By: neil
State-Changed-When: Sat Sep  1 02:15:17 2001
State-Changed-Why:
    Digraphs are part of the standard; if you don't like it you need to get the
    standard changed.  I don't want a -no-digraphs option.
    Your code might only break on GCC now, but it will break on other
    compilers too in the future.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=4190&database=gcc


             reply	other threads:[~2001-09-01  2:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-01  2:15 neil [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-08-31 20:56 ballan

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=20010901091518.29952.qmail@sourceware.cygnus.com \
    --to=neil@gcc.gnu.org \
    --cc=ballan@c425089-a.plstn1.sfba.home.com \
    --cc=gcc-bugs@gcc.gnu.org \
    --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: link
Be 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).