Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!crdgw1!uunet!medar!jseymour
From: jseymour@medar.com (James Seymour)
Newsgroups: comp.lang.c
Subject: ANSI Standards
Keywords: declarations, prototyping, returns
Message-ID: <104@hdwr1.medar.com>
Date: 3 Apr 91 14:58:46 GMT
Distribution: usa
Organization: Medar, Inc.     Farmington Hills, MI
Lines: 32

Well, I've mangaged to get my backside in hot water in other newsgroups
lately, why not here as well :-).

We're getting ready to update our in-house Software Quality Assurance
Plan (which includes some "style" guidlines to make things easier for
multi-programmer projects), and there are some issues we want to address
and I'm looking for some direction.  There are two points:

1) We've been using the K&R format for function definitions, while the
   new ANSI format is like the Pascal format (for example).  The K&R
   Second Edition states that the original K&R form will be supported
   at least during the "transition period".  Does the ANSI standard
   eliminate the original K&R format (eventually)?  Even if it doesn't,
   does it look like that's the way "everybody" will be doing it in the
   future?  Btw: I've yet to see code from any source using the new
   ANSI format, other than examples in some texts.

2) Parenthesis are not required for return statements, but according to
   the Second Edition K&R work, they are, and will remain, acceptable.
   I *have* seen lots of code where the parens are not used.  Does this
   seem to be the way most folks are heading?  If so, why?

(Personally, I prefer the original K&R forms for both of these, as do
 most of the engineers here).

Thanks in advance for any feedback.

-- 
Jim Seymour				| Medar, Inc.
...!uunet!medar!jseymour		| 38700 Grand River Ave.
jseymour@medar.com			| Farmington Hills, MI. 48331
CIS: 72730,1166  GEnie: jseymour	| FAX: (313)477-8897