Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!wuarchive!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!nic.MR.NET!shamash!tank!gargoyle!ddsw1!olsa99!oct1!proxima!lucio
From: lucio@proxima.UUCP (Lucio de Re)
Newsgroups: comp.lang.c
Subject: Re: C style peeve and knowing the rules
Message-ID: <1273@proxima.UUCP>
Date: 7 Apr 90 12:13:08 GMT
References: <1990Mar26.023758.21002@athena.mit.edu>
Reply-To: lucio@proxima.UUCP (Lucio de Re)
Organization: FLAGSHIP Wide Area Networks - Cape Town
Lines: 24

In article <1990Mar26.023758.21002@athena.mit.edu> scs@athena.mit.edu (Steve Summit) writes:
>I stopped using parentheses after "return" because I happen to
>mistype that particular keyword a lot, and
> 
>        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.
Unfortunately, I like to think of return (); as equivalent to exit ();
(how eccentric (a euphemism for perverse) can one get?) so _I_ will
stick to return(x); (or retrun(x), my personal misspelling).

----------------------------------------------------------------------
I used to design nuclear reactors and you should see the code that
engineers and scientists come up with. Yuuuck! Spaghetti everywhere.
-------------------------------------------------- (Kenneth L Moore) -
Lucio de Re                        ...uunet!ddsw1!olsa99!proxima!lucio
-------------------------------------------------------- lucio@proxima
                Disclaimer: He must have been joking!