Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!linus!philabs!cmcl2!seismo!umcp-cs!chris
From: chris@umcp-cs.UUCP (Chris Torek)
Newsgroups: net.lang.c,net.bugs,net.unix-wizards
Subject: Re: weird C-compiler error message
Message-ID: <1926@umcp-cs.UUCP>
Date: Sat, 7-Jun-86 01:28:18 EDT
Article-I.D.: umcp-cs.1926
Posted: Sat Jun  7 01:28:18 1986
Date-Received: Tue, 10-Jun-86 01:03:54 EDT
References: <1297@burl.UUCP>
Reply-To: chris@maryland.UUCP (Chris Torek)
Organization: University of Maryland, Dept. of Computer Sci.
Lines: 23
Xref: linus net.lang.c:8559 net.bugs:738 net.unix-wizards:15257

In article <1297@burl.UUCP> rcj@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@umcp-cs		ARPA:	chris@mimsy.umd.edu