Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/18/84; site brl-tgr.ARPA Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!godot!harvard!seismo!brl-tgr!tgr!gwyn@Brl-Vld.ARPA From: Doug Gwyn (VLD/VMB)Newsgroups: net.lang.c Subject: Re: SIZEOF Message-ID: <8171@brl-tgr.ARPA> Date: Sat, 9-Feb-85 19:00:13 EST Article-I.D.: brl-tgr.8171 Posted: Sat Feb 9 19:00:13 1985 Date-Received: Mon, 11-Feb-85 05:37:44 EST Sender: news@brl-tgr.ARPA Organization: Ballistic Research Lab Lines: 8 There is no way, with separate compilation of modules, that a current C compiler can determine what pointer type to coerce a 0 function argument to, which is why the programmer must do this himself. In the draft ANSI C standard, if a function prototype is specified then it will indeed be possible (and required) that the compiler coerce an argument to the right type. Actually, some of us don't like this since it hides coding errors; it would be nice if the compiler (or at least lint) could give a warning when this coercion was done.