Xref: utzoo comp.lang.c:34180 alt.religion.computers:2089
Path: utzoo!utgpu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!van-bc!ubc-cs!news-server.csri.toronto.edu!clyde.concordia.ca!thunder.mcrcim.mcgill.edu!quiche!homer!utility
From: utility@quiche.cs.mcgill.ca (Ronald BODKIN)
Newsgroups: comp.lang.c,alt.religion.computers
Subject: Re: ANSI C prototypes
Message-ID: <75@homer.cs.mcgill.ca>
Date: 23 Nov 90 22:30:46 GMT
References: <1005@christopher-robin.cs.bham.ac.uk> <1906@necisa.ho.necisa.oz>
Followup-To: comp.lang.c
Organization: SOCS - Mcgill University, Montreal, Canada
Lines: 12

In article <1906@necisa.ho.necisa.oz> boyd@necisa.ho.necisa.oz (Boyd Roberts) writes:
>Right on!  The function prototypes are just stupid.  I shouldn't have to go:

>    extern gore	*good(const char *vomit);

>to get the functionality of type checking of function arguments.
>The compiler and loader should do it.
	However, one prototype will allow you to automatically coerce
things like ints to longs/floats/doubles or "near" pointers to "far"
pointers, etc.  Also, it is much faster to catch a prototype problem
before linking a large application.
	Ron