consistency in declaration

Alastair Dallas awd at dbase.UUCP
Fri Jun 16 03:41:38 AEST 1989


In article <64 at BLEKUL11.BITNET>, SAAAA04 at BLEKUL11.BITNET (Saaaa04) writes:
> To my surprise the following happened with the waterloo C compiler
> it refuses:
> 
> void foo(int , int y);
> 
> but (of course) accepts:
> 
> void foo(int x, int y);
> void foo(int , int);
> 
> Do I have to be consistent ? Or is this a bug in the compiler ?
> 

The same seems to be true for Microsoft C v5.1 for the IBM PC.  But is 
consistency really that much of a burden in this case?

/alastair/



More information about the Comp.lang.c mailing list