weird C-compiler error message
Chris Torek
chris at umcp-cs.UUCP
Sat Jun 7 15:28:18 AEST 1986
In article <1297 at burl.UUCP> rcj at burl.UUCP (Curtis Jackson) writes:
[code such as]
>int f1, f2; /* other variable declarations, too */
>main(argc,argv)
>int argc, f1, f2;
[produces]
>27: warning: bad arg temp
>30: warning: bad arg temp
The `temp' referred to is, of course, entirely in the mind of the
compiler. I was, however, surprised that PCC emits a warning for
this; it seems to me it should be classified as a compiler error.
Whether the message
"foo.c", line 27: compiler error: bad arg temp
would be any less confusing is uncertain.
--
In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 1516)
UUCP: seismo!umcp-cs!chris
CSNet: chris at umcp-cs ARPA: chris at mimsy.umd.edu
More information about the Comp.lang.c
mailing list