Path: utzoo!attcan!uunet!husc6!cmcl2!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn )
Newsgroups: comp.lang.c
Subject: Re: Beware the implicit function declaration!
Message-ID: <8937@smoke.BRL.MIL>
Date: 20 Nov 88 01:54:47 GMT
References: <4264@bnrmtv.UUCP>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 15

In article <4264@bnrmtv.UUCP> rapin@bnrmtv.UUCP (Eric Rapin) writes:
>... Maybe a good suggestion to the ANSI "C" committee would be to
>allow the programmer to turn off the default int declaration of
>functions to force you to always declare them explicitly.

I'm posting my response (which should not be taken as an official
X3J11 position) because it may be of general interest:

X3J11 (the ANSI C committee) didn't want to try to dictate any
details of how C compilers are invoked, and they didn't want to
specify any form of multiple "levels" of the standard.  Vendors
will in many cases provide a variety of options, but only the
standard-conforming mode of operation will be covered by the
ANSI/ISO C standard specification.  You can try to convince your
compiler vendor that the option you suggest is a good idea..