public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Florian Weimer <fw@deneb.enyo.de>
To: Karel Gardas <kgardas@objectsecurity.com>
Cc: gcc@gcc.gnu.org
Subject: Re: gcc 2.95.x interesting c++ parser error (bug).
Date: Sun, 21 Apr 2002 15:05:00 -0000	[thread overview]
Message-ID: <87wuv07nwd.fsf@deneb.enyo.de> (raw)
In-Reply-To: <Pine.LNX.4.43.0204212027100.476-100000@thinkpad.objectsecurity.cz> (Karel Gardas's message of "Sun, 21 Apr 2002 20:29:09 +0200 (CEST)")

Karel Gardas <kgardas@objectsecurity.com> writes:

> On Sun, 21 Apr 2002, Florian Weimer wrote:
>
>> Karel Gardas <kgardas@objectsecurity.com> writes:
>>
>> > because it takes me some time to find exact place in my sources which
>> > cause this bug (these sources are of course perfectly OK with gcc 3.1).
>>
>> The sources aren't perfectly okay.  You must not use identifiers with
>> two leading underscores (see section 17.4.3.1.2 in ISO/IEC 14882).
>
> Interesting, but it's described in GNU C++ coding style (for libstdc++) to
> use double underscores for local (temporary) variable and method/function
> parameters.

Well, 17.4.3.1.2 reserves these identifiers to implementors, so you
can expect implementors to use them. ;-)

  reply	other threads:[~2002-04-21 21:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-20  8:28 Karel Gardas
2002-04-21  4:32 ` Florian Weimer
2002-04-21 11:47   ` Karel Gardas
2002-04-21 15:05     ` Florian Weimer [this message]
2002-04-25  3:31       ` Jason Merrill
2002-04-25  8:45         ` Karel Gardas
2002-04-25 10:59           ` Phil Edwards

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=87wuv07nwd.fsf@deneb.enyo.de \
    --to=fw@deneb.enyo.de \
    --cc=gcc@gcc.gnu.org \
    --cc=kgardas@objectsecurity.com \
    /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).