Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!linus!decvax!genrad!grkermit!mit-vax!eagle!mhuxt!mhuxi!cbosgd!ihnp4!we13!otuxa!ll1!sb1!burl!duke!mcnc!idis!mi-cec!raz From: raz@mi-cec.UUCP Newsgroups: net.lang.c Subject: Bogus compiler error messages Message-ID: <120@mi-cec.UUCP> Date: Mon, 18-Jul-83 17:32:44 EDT Article-I.D.: mi-cec.120 Posted: Mon Jul 18 17:32:44 1983 Date-Received: Tue, 19-Jul-83 13:25:08 EDT Lines: 26 Here's a good one, folks. I just got the following result when I compiled a program: % cc foo.c /tmp/ctm311596 m 0422 % well, I can recognize a file created by maketemp(), but 'm 0422'?. The temp file does not even exist! It turns out that this 'error message' is caused by the assembler picking up a label that the compiler generated, and not being able to distinguish it from a similar label: writeStats() becomes ~~writeSt, and writeStrain() becomes ~~writeSt. @FLAME( this is bogus!!! ) I don't mind being limited to 6 character function names, so much as having to go through the assembler code to find a compiler error. To the powers that be: FIX IT! Robert A Zimmermann {decvax!idis!mi-cec!}raz