Path: utzoo!telly!attcan!uunet!tut.cis.ohio-state.edu!kithrup.com!sef
From: sef@kithrup.com (Sean Eric Fagan)
Newsgroups: gnu.gcc.bug
Subject: function prototype syntax
Message-ID: <9002270429.AA25851@ucscc.UCSC.EDU>
Date: 27 Feb 90 04:20:48 GMT
Sender: daemon@tut.cis.ohio-state.edu
Distribution: gnu
Organization: GNUs Not Usenet
Lines: 20

>I tried compiling the same program with Microsoft C 5.1, and it said
>unto me, quote,
>	junk3.c(1) : error C2059: syntax error : ','
>I promptly got on the phone to Microsoft to chew them out about this
>obvious ANSI non-compatibility.  The fella on the phone said, "No, the
>ANSI standard requires that you either name all the arguments in a
>function prototype, or none of them".  Therefore, he claimed, the
>error generaed by Microsoft was correct (although not very
>informative).
	
uSoft is pulling your leg, and it's something they will be having
problems with.  At one point, I believe that the standard did require
either all unnamed, or all named; now, it can be mixed.  uSoft has not
updated their compiler for this.  People using SCO's Compiler have
the same problem, of course, but it will be fixed shortly (I have it
on good authority from the person who does the compiler work [me 8-)]
that it is fixed, along with some other ANSI-isms).  Sorry for the plug,
of course, but this was largely informational.

Sean.