Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!nike!sgi!msc
From: msc@sgi.UUCP (Mark Callow)
Newsgroups: comp.lang.c++
Subject: Re: cfront: internal error
Message-ID: <151@sgi.UUCP>
Date: Tue, 18-Nov-86 14:59:36 EST
Article-I.D.: sgi.151
Posted: Tue Nov 18 14:59:36 1986
Date-Received: Tue, 18-Nov-86 21:37:36 EST
References: <644@comp.lancs.ac.uk> <6348@alice.UUCP>
Organization: Silicon Graphics Inc, Mountain View, CA
Lines: 40
Summary: c++ error recovery

In article <6348@alice.UUCP>, bs@alice.UUCP writes:
> 
> stephen @ Department of Computing at Lancaster University, UK. writes:
> 
> > One of my colleagues had a program which caused cfront to fail with an internal
> > error as its first error message.
> 
> (1) Clearly internal errors should not happen so there is a cfront bug.
> 
> 
> (3) This message is not precise enough to allow anyone to avoid or fix the
> 	problem. Please give us the benefit of your experienc; please don't
> 	just tease us with ``there is a bug somewhere''.

I resisted the temptation to reply to the Stephen's message with a report
of my own since I was so sure that others, including Bjarne, must be aware
of the problem that I would be simply flaming at c++'s error recovery.  However
in the light of the above response ...

I left out the ";" in the hello world program.  I.e.

#include <stream.h>

main()
{
	cout << "Hello, world\n"
}

and was rewarded with the message:

"hello.c", line 7: internal <<cfront 05/20/86>> error: bus error (or something nasty like that)

I put this down to the typically lousy error recovery I have experienced in
UNIX compilers in the past.  I'm really happy to hear that Bjarne is interested
in fixing the problem.
-- 
From the rematerialised TARDIS of Mark Callow
msc@sgi.uucp,  sgi!msc@decwrl.dec.com ...{decwrl,sun}!sgi!msc
"Painting, n. The art of protecting flat surfaces from the weather and
exposing them to the critic."