Xref: utzoo comp.lang.c:15462 gnu.gcc:146
Path: utzoo!attcan!uunet!tut.cis.ohio-state.edu!rutgers!labrea!mcnc!rti!xyzzy!meissner
From: meissner@xyzzy.UUCP (Michael Meissner)
Newsgroups: comp.lang.c,gnu.gcc
Subject: Re: typechecking
Keywords: typechecking, lint
Message-ID: <2800@xyzzy.UUCP>
Date: 12 Jan 89 22:21:22 GMT
References: <19620@uflorida.cis.ufl.EDU> <9335@smoke.BRL.MIL>
Reply-To: meissner@dg-rtp.UUCP (Michael Meissner)
Organization: Data General (Languages @ Research Triangle Park, NC.)
Lines: 26

(Gnu.gcc people -- this appeared in comp.lang.c on USENET)

In article <9335@smoke.BRL.MIL> gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>) writes:
| In article <19620@uflorida.cis.ufl.EDU> thoth@banana.cis.ufl.edu () writes:
| >fprintf("%s : line %d : colon expected.\n",filename,linenumber); 
| >Turbo catches this and gcc doesn't.
| 
| I'm somewhat surprised that GCC doesn't catch this, since the
| correct prototype in <stdio.h> would be
| 	int fprintf(FILE *, const char *, ...);
| and the compiler should be able to validate the first two argument types.

Actually, GCC will report the type mismatch providing whomever
installs it adds prototypes to the standard header files.  The
original author consider taking the time to do it (and hopefully add
smarts to `fixincludes' to do this automagically for future
revisions).  After all, GNU is a cooperative effort.
 --
Michael Meissner, Data General.

Uucp:	...!mcnc!rti!xyzzy!meissner
Arpa:	meissner@dg-rtp.DG.COM   (or) meissner%dg-rtp.DG.COM@relay.cs.net
-- 
Michael Meissner, Data General.

Uucp:	...!mcnc!rti!xyzzy!meissner
Arpa:	meissner@dg-rtp.DG.COM   (or) meissner%dg-rtp.DG.COM@relay.cs.net