Xref: utzoo comp.std.c:1151 gnu.gcc:497
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!sharkey!mcf!elsie!ado
From: ado@elsie.UUCP (Arthur David Olson)
Newsgroups: comp.std.c,gnu.gcc
Subject: gcc 1.35 conflicting types message?
Message-ID: <9101@elsie.UUCP>
Date: 5 May 89 02:31:28 GMT
Followup-To: posterposter
Organization: NIH-LEC, Bethesda, MD
Lines: 29

The GNU C Compiler, version 1.35, now generates a "conflicting types" message
and refuses to compile when confronted with code such as. . .

	Script started on Thu May  4 22:03:53 1989
	elsie$ cat try.c
	extern int	whatever();
	extern int	whatever(char * format, ...);
	elsie$ /usr/local/bin/gcc -v try.c
	gcc version 1.35
	 /usr/local/lib/gcc-cpp -v -undef -D__GNUC__ -Dmc68000 -Dsun -Dunix -D__mc68000__ -D__sun__ -D__unix__ -D__HAVE_68881__ -Dmc68020 try.c /tmp/cca15784.cpp
	GNU CPP version 1.35
	 /usr/local/lib/gcc-cc1 /tmp/cca15784.cpp -quiet -dumpbase try.c -version -o /tmp/cca15784.s
	GNU C version 1.35 (68k, MIT syntax) compiled by GNU C version 1.35.
	try.c:2: conflicting types for `whatever'
	try.c:2: A parameter list with an ellipsis can't match
	try.c:2: an empty parameter name list declaration.
	try.c:1: previous declaration of `whatever'
	elsie$ exit

	script done on Thu May  4 22:04:12 1989

If you can tell me wheter "try.c" above is [d[p]]ANS-compliant or not,
I'd appreciate hearing from you by electronic mail.  I'd also appreciate
opinions on whether the code should be accepted even if it isn't compliant,
so that newly written header files can contain prototypes without introducing
the possibility of clashes with old-style header files.
-- 
			Space:  Canada, 0 tries ever.
	Arthur David Olson    ado@ncifcrf.gov    ADO is a trademark of Ampex.