home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.software-eng
- Path: sparky!uunet!psinntp!dscope!jld
- From: jld@datascope.com (Jay L. Davis)
- Subject: Re: C code Layout
- Message-ID: <1992Dec15.160408.7367@datascope.com>
- Keywords: C code layout
- Organization: Datascope Corp.
- References: <1992Dec12.122453.8582@seq.uncwil.edu>
- Date: Tue, 15 Dec 1992 16:04:08 GMT
- Lines: 23
-
- In article <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.
- >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.
- >Too many comments that try to say what the code is saying are IMHO
- >distracting. The code in this case was assembler. Since that time
- >higher level languages came into use. In particular C language.
- >My philosophy is to let the language speak for itself. Add comments
- >where necessary. Again while directing the efforts of hundreds of
- >people on the Safequard Anti-Balistic Missile System, we set standards
- >for commenting that let the code be seen. The project met its objectives
- >and schedule -- one of the few in that time frame.
- >Flame on and damned be he or she who flames out.
-
- About time I heard some common sense in this discussion. One other point that
- is real important, if your code is a maze, you need a detailed map. If it
- is organized (designed) well, you don't have to explain it as much, it should
- be obvious.
-
- ---Jay Davis
-