home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!spool.mu.edu!agate!stanford.edu!rock!concert!borg!news_server!martinc
- From: martinc@grover.cs.unc.edu (Charles R. Martin)
- Newsgroups: comp.software-eng
- Subject: Re: C Code Layout
- Message-ID: <MARTINC.92Dec14201208@grover.cs.unc.edu>
- Date: 15 Dec 92 01:12:08 GMT
- References: <1992Dec14.193111.20367@seq.uncwil.edu>
- Sender: news@cs.unc.edu
- Organization: UNC Department of Computer Science
- Lines: 22
- In-reply-to: herbst@seq.uncwil.edu's message of 14 Dec 92 19:31:11 GMT
-
- In article <1992Dec14.193111.20367@seq.uncwil.edu> herbst@seq.uncwil.edu (R.T. Herbst) writes:
-
- I learned my lesson. Comments are essential.
- Comments that obscure the code can make
- reading the code very difficult.
- The code is where the actions is.
- C language permits alongside commenting
- So comment along side the code.
- This allows the code to be continuous.
- Well commented code is needed, but
- Commenting is a small part of the entire process.
- I doubt that there will ever be a agreement on this
- subject. So what.
-
- Well, there is the old idea of dialectic as an effort to find Truth, I
- suppose.
- --
- Charles R. Martin/(Charlie)/martinc@cs.unc.edu
- Dept. of Computer Science/CB #3175 UNC-CH/Chapel Hill, NC 27599-3175
- 3611 University Dr #13M/Durham, NC 27707/(919) 419 1754
- "Oh God, please help me be civil in tongue, pure in thought, and able
- to resist the temptation to laugh uncontrollably. Amen." -- Rob T
-