Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!ucsd!helios.ee.lbl.gov!pasteur!cory.Berkeley.EDU!klatchko
From: klatchko@cory.Berkeley.EDU (ron klatchko)
Newsgroups: comp.lang.c
Subject: Re: C style peeve and knowing the rules
Message-ID: <23845@pasteur.Berkeley.EDU>
Date: 9 Apr 90 21:17:06 GMT
References: <1990Mar26.023758.21002@athena.mit.edu> <1273@proxima.UUCP>
Sender: news@pasteur.Berkeley.EDU
Reply-To: klatchko@cory.Berkeley.EDU.UUCP (ron klatchko)
Organization: University of California, Berkeley
Lines: 19
X-Local-Date: 9 Apr 90 14:17:06 PDT

In article <1273@proxima.UUCP> lucio@proxima.UUCP (Lucio de Re) writes:
>In article <1990Mar26.023758.21002@athena.mit.edu> scs@athena.mit.edu (Steve Summit) writes:
>>        retunr x;
>>is a compile-time error, while
>>        retunr(x);
>>doesn't complain until link time.  Admittedly a minuscule point.
>
>Not at all, I think it's a very good point; in fact the best to date.

It is a good point, if you are using a compiler that cannot handle
prototypes.  Otherwise, make sure that your compiler will issue a
warning if it you call a function that is not prototyped (in gcc, this
can be done using -Wimpilict or -Wall; in Microsoft C, this can be
done using -W3).  You can then indulge your personal style peeve and
still find out about a typo at compile time.

ron
------------------------------------------------------------------------------
Ron Klatchko         klatchko@cory.Berkeley.EDU       ...!ucbvax!cory!klatchko