Article View: comp.std.c
Article #4971Re: Prefixing functions with return type..
From: Kevin D. Quitt
Date: Sat, 30 Mar 1996 20:49
Date: Sat, 30 Mar 1996 20:49
18 lines
1570 bytes
1570 bytes
On Mon, 18 Mar 96 20:16:16 GMT, Adrian P Stephens <aps@symbionics.co.uk> >Ours >has "C" coding standards which require this kind of thing. Initially >I was against it, because it makes things cluttered, lengthens lines >of code and makes for more typing. It does more than that: it makes the code less supportable. When the type of a variable has to change, every occurence of it has to be changed in the text. It also goes against the philosophical ideal of information hiding, and lulls the user into not having the compiler/lint perform strict type-checking (since 'it's obvious' what the type is). I think it's better to give a variable a human-meaningful name that describes its function, and use the compiler to enforce and report typing problems. -- #include <standard_disclaimer.h> http://emoryi.jpl.nasa.gov/ _ Kevin D Quitt USA 91351-4454 96.37% of all statistics are made up
Technical Details
Message-ID:
<315d9d7f.10160930@netline-fddi.jpl.nasa.gov>Path:
arc1-ca.pugleaf.net!netline-fddi.jpl.nasa.gov!usenetReferences:
<4hstf8$jf3@cybernews.cyberus.ca> <1996Mar14.080731.15076@Watt.COM> <1996Mar18.201616.6958@Watt.COM>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!netline-fddi.jpl.nasa.gov!usenet From: kdq@emoryi.jpl.nasa.gov (Kevin D. Quitt) Newsgroups: comp.std.c Subject: Re: Prefixing functions with return type.. Date: Sat, 30 Mar 1996 20:49:54 GMT Organization: Jet Propulsion Laboratory Message-ID: <315d9d7f.10160930@netline-fddi.jpl.nasa.gov> References: <4hstf8$jf3@cybernews.cyberus.ca> <1996Mar14.080731.15076@Watt.COM> <1996Mar18.201616.6958@Watt.COM> Reply-To: kdq@emoryi.jpl.nasa.gov NNTP-Posting-Host: emoryi.jpl.nasa.gov Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Newsreader: Forte Agent .99d/32.182