Re: gcc 2.95.x interesting c++ parser error (bug).

[Karel Gardas <kgardas@objectsecurity.com>]

On Thu, 25 Apr 2002, Jason Merrill wrote:

> >>>>> "Florian" == Florian Weimer <fw@deneb.enyo.de> writes:
>
> > 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. ;-)
>
> Exactly.  They are used in libstdc++ specifically because you (as a user)
> aren't allowed to use them, so they can't conflict with any macros you
> might define.

Yes, I see, but I like this coding style. :-( Is there any prefered GNU
coding style for c++ projects?

Thanks,

Karel
--
Karel Gardas                  kgardas@objectsecurity.com
ObjectSecurity Ltd.           http://www.objectsecurity.com