Re: comments on comments on comments

[rfarris@serene.UUCP (Rick Farris)]

In article <4534@hubcap.UUCP> wtwolfe@hubcap.clemson.edu writes:

| I use a tactic which essentially makes comments as inherent a part of
| the code as possible: I make all package, procedure, function, type,
| and variable names as descriptive as reasonably possible.

[some examples deleted]

Yes, this is the only way I've seen documentation that tended to be
maintained with the code.  Personally, I'm a proponent of 4th
generation reverse engineering tools to do things like structure
charts, etc, since they are *never* maintained if it has to be done
manually. 


| Also, I've learned to type very quickly, through long hard experience.  :=)


As the ADAge goes, "Programs are *written* once, but *read* many times."


Rick Farris   RF Engineering  POB M  Del Mar, CA  92014   voice (619) 259-6793
rfarris@serene.cts.com     ...!uunet!serene!rfarris       serene.UUCP 259-7757