home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.software-eng
- Path: sparky!uunet!enterpoop.mit.edu!spool.mu.edu!mixcom.com!amby
- From: amby <amby@mixcom.mixcom.com>
- Subject: Re: C code Layout
- Organization: Milwaukee Internet Xchange BBS, Milwaukee, WI U.S.A.
- Distribution: usa
- Date: Sun, 13 Dec 1992 15:24:30 GMT
- Message-ID: <1992Dec13.152430.6370@mixcom.com>
- References: <1992Dec12.122453.8582@seq.uncwil.edu>
- Keywords: C code layout
- Sender: ttvvtt@mixcom.com (Donald Amby)
- Lines: 27
-
- In <1992Dec12.122453.8582@seq.uncwil.edu> herbst@seq.uncwil.edu (R.T. Herbst) writes:
-
- >While directing the eforts of 125 people in producing the
- >A Data switching system for the Bell System- Good ol'
- >Ma bell-- I asked for a sample of code. I founr the comments to
- >be utter nonsense,. If one removed the code, the comments made no sense.
-
- Excellent point! The comments SHOULD make sense without the code.
- I personally write code by doing the comments first. If I cannot
- describe in clear concise sentences what I am attempting to do,
- then I obviously do not understand the problem.
-
- I then add the code as I get the details of the implementation
- worked out.
-
- >It was better to let the code speak for itself. If fact the code
- >was hidden in by the comments. Certainly we need well commented code.
-
- Organizations that are serious about quality should address the
- comments as part of any code review. Of course, if there are
- no code reviews you will never see the comments until you have
- to make changes to the code.
- --
- Donald E. Amby
- don@amby.mixcom.com (for short mail) (414)797-6713 (voice)
- amby@eisner.decus.org (for lengthy mail) (414)797-6533 (FAX)
- Harnischfeger Engineers, Inc., P.O.Box 1512, Milwaukee, WI 53201-1512
-