Re: Compiler parsing error

Re: Compiler parsing error

[Chris Butler]

Hi,

> The accompanying file seems to blow up the parser. I successfully compile
> and run it with the Borland C++ beta.

Once I added #include <algo.h> (for replace), it compiled fine on an
i586-pc-cygwin target.

By the way - you should read http://egcs.cygnus.com/faq.html#bugreport for
information on what details you should provide in a bug report.

--
Chris Butler
<chrisb@sandy.force9.co.uk>

Re: Compiler parsing error

[Joe Buck]

> There was a problem with a missing <algorithm> include, but the parser
> blowup still remains. The problem was in the use of "dos" or "unix" as an
> identifier; once I changed them to _dos and _unix it compiled. But it should
> not have generated a parser error. This was with the egcs snapshot from two
> weeks ago under RedHat Linux 5.2.

The -ansi flag will turn off preprocessor identifiers that are in the
reserved namespace.  Unfortunately if they are turned off by default,
important packages like the X Window system fails to build.

Re: Compiler parsing error

[Bruce Eckel]

There was a problem with a missing <algorithm> include, but the parser
blowup still remains. The problem was in the use of "dos" or "unix" as an
identifier; once I changed them to _dos and _unix it compiled. But it should
not have generated a parser error. This was with the egcs snapshot from two
weeks ago under RedHat Linux 5.2.
=============================
Bruce Eckel    http://www.BruceEckel.com
Contains free electronic books: "Thinking in Java" & "Thinking in C++ 2e"

-----Original Message-----
From: Chris Butler <chrisb@sandy.force9.co.uk>
To: Bruce Eckel <Bruce@EckelObjects.com>; egcs@cygnus.com <egcs@cygnus.com>
Date: Sunday, December 27, 1998 1:27 AM
Subject: Re: Compiler parsing error


>Hi,
>
>> The accompanying file seems to blow up the parser. I successfully compile
>> and run it with the Borland C++ beta.
>
>Once I added #include <algo.h> (for replace), it compiled fine on an
>i586-pc-cygwin target.
>
>By the way - you should read http://egcs.cygnus.com/faq.html#bugreport for
>information on what details you should provide in a bug report.
>
>--
>Chris Butler
><chrisb@sandy.force9.co.uk>
>
>
>