Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!apple!usc!hacgate!ashtate!dbase!awd
From: awd@dbase.UUCP (Alastair Dallas)
Newsgroups: comp.lang.c
Subject: Re: consistency in declaration
Summary: Same for Microsoft C
Message-ID: <115@dbase.UUCP>
Date: 15 Jun 89 17:41:38 GMT
References: <64@BLEKUL11.BITNET>
Organization: Ashton Tate Devlopment Center Glendale, Calif.
Lines: 18

In article <64@BLEKUL11.BITNET>, SAAAA04@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/