Xref:	news-dnh.mv.net comp.os.msdos.djgpp:211
Path:	news-dnh.mv.net!mv!news.sprintlink.net!howland.reston.ans.net!vixen.cso.uiuc.edu!uwm.edu!fnnews.fnal.gov!stc06.ctd.ornl.gov!cs.utk.edu!duncan.cs.utk.edu!doolin
From:	doolin AT duncan DOT cs DOT utk DOT edu (David Doolin)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: VOTE: CODE STANDARDS
Date:	7 Jun 1995 13:38:14 GMT
Organization:	University of Tennessee Computer Science
Lines:	21
Distribution:	world
References:	<D9rwAu DOT AI9 AT jade DOT mv DOT net>
Reply-To:	doolin AT cs DOT utk DOT edu
Nntp-Posting-Host:	duncan.cs.utk.edu
To:	djgpp AT sun DOT soe DOT clarkson DOT edu
Dj-Gateway:	from newsgroup comp.os.msdos.djgpp

In article <D9rwAu DOT AI9 AT jade DOT mv DOT net>, lorin lund <Lorin DOT Lund AT LDDSNet DOT Com> writes:
|>      This thread is long and iteresting in the feelings it stirs.

|>      
|>      My experience is that those of my colleagues that write good comments 
|>      write such organized code that the comments are hardly necessary.  
|>      Those who write code that functions correctly but is harder to read, 
|>      usually have their minds so much into the program that anything they 
|>      write wouldn't make much sense to the un-initiated anyway.
|>      

I make one point here: for those of us who are not full time programmers or
cs types, but merely use C on a semi weekly basis (rather than daily),
comments are vital and necessary.  I find it hard to remember my own code
after a few weeks unless it is fully documented.  I also find that writing 
comments *before* coding can help me logically structure a program.

Dave Doolin             Institute for Geotechnology
doolin AT cs DOT utk DOT edu       Department of Civil Eng. UTK	

- Raw text -