From: "Bruce Eckel" <Bruce@EckelObjects.com>
To: "Chris Butler" <chrisb@sandy.force9.co.uk>, <egcs@cygnus.com>
Subject: Re: Compiler parsing error
Date: Mon, 28 Dec 1998 10:53:00 -0000 [thread overview]
Message-ID: <01f101be3292$aa032760$0c00a8c0@peppy> (raw)
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>
>
>
>
next reply other threads:[~1998-12-28 10:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-12-28 10:53 Bruce Eckel [this message]
1998-12-28 11:03 ` Joe Buck
-- strict thread matches above, loose matches on Subject: below --
1998-12-27 1:27 Chris Butler
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='01f101be3292$aa032760$0c00a8c0@peppy' \
--to=bruce@eckelobjects.com \
--cc=chrisb@sandy.force9.co.uk \
--cc=egcs@cygnus.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).