stephen@comp.lancs.ac.uk (Stephen J. Muir) (11/12/86)
One of my colleagues had a program which caused cfront to fail with an internal error as its first error message. The problem was caused by the fact that he put a ; after every }. Now, in my view, cfront should make up its mind either to accept this or not. -- EMAIL: stephen@comp.lancs.ac.uk | Post: University of Lancaster, UUCP: ...!mcvax!ukc!dcl-cs!stephen | Department of Computing, Phone: +44 524 65201 Ext. 4120 | Bailrigg, Lancaster, UK. Project:Alvey ECLIPSE Distribution | LA1 4YR
bs@alice.UUCP (11/15/86)
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. The problem was caused by the fact that he > put a ; after every }. Now, in my view, cfront should make up its mind either > to accept this or not. (1) Clearly internal errors should not happen so there is a cfront bug. (2) Cfront should implement C++, not ``make its mind up'' about what to accept. (3) There are (confusingly enough) cases in C++ (as in C) where a ; after a } is illegal. For example: ; if (a) { f1(); g1(); }; else { f2(); g2(); }; ^ ^ syntax error--^ ok --^ (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''.
msc@sgi.UUCP (Mark Callow) (11/18/86)
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."
jaap@mcvax.UUCP (Jaap Akkerhuis) (11/19/86)
In article <151@sgi.UUCP> msc@sgi.UUCP (Mark Callow) writes: > #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. H'm, why didn't you tried it again? I did, and this is the result: Script started on Wed Nov 19 14:28:06 1986 You have mail. mcvax> cat t.c #include <stream.h> main() { cout << "Hello, stupid\n" } mcvax> CC t.c CC t.c: "t.c", line 5: error: ';' expected at end of statement or declaration before '}' 1 error mcvax> Script done... jaap
mikem@otc.OZ (Michael Mowbray) (11/20/86)
In article <151@sgi.UUCP> Mark Callow (msc@sgi.uucp) writes: > 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 presume this is only in old versions. On our recently-arrived release 1.1 I get the following: CC hello.c: "hello.c", line 6: error: ';' expected at end of statement or declaration before '}' 1 error which is fine. This reminds me of a problem we had when re-writing error.c to use varargs. The person doing the re-write made a minor error in the types. Varargs couldn't handle things which were cast to int when put on the stack. This strangely caused the error messages to contain obscure references to "tokenX" instead of the character it actually meant (e.g: the ';' above) and the solution in that case was to use int's rather than short's. I'm wondering if there are other subtle porting traps that make one angry at cfront when it's really just a bad port. Mike Mowbray Senior Engineer Systems Development Overseas Telecommunications Commission (Australia) UUCP: {seismo,mcvax}!otc.oz!mikem ACSnet: mikem@otc.oz