Yur rite MikE ... its kinda like spellin ... as long as it werks its ok!
 - Nick -

Mike M wrote:
>
> I dont understand the big deal that people have with comments and blank lines?
?? who cares > really. if u have to turn in your program to someone yes it would
 be nice if u made it look neat > and indent and comment lines etc.  if your cod
ing for yourself and no ones ever gonna see it > anyway who cares.  If your codi
ng and someone wants help and u send them a sample of your code so > they get th
e idea and there are no comments in there...its their problem.  Lets face it com
ments > and "prettyness" are unnecissary, they are not included in the final pac
kage they are mearly a > convience when re-reading some of your old stuff so you
 or those u work with know whats going on > quickly and easily.
>
> MikE
> PS.. I never comment, because if anyone gets my code...i hope they do get conf
used : )  j/k hehe
>
> On Fri, 19 Nov 1999 08:12:48 +1100 "Paul B. Webster VK2BZC" <paulb@MIDCOAST.CO
M.AU> wrote:
> >Richard Martin wrote:
> >
> >> A very bright programer once worked for me who felt that
> >> "unnecessary <newlines> (CR/LF) and spaces got in the way (in 'C')"
> >
> >  I gather you are referring to the habit of putting multiple
> >expressions per line.
> >
> >  What does make code *very* unreadable however is the practice of
> >double-spacing.  A single blank line between functional blocks doesn't
> >hurt (In assembler, a blank line after a "GOTO" or "BRA", except in PIC
> >code where GOTOs follow skips of course in which case indentation is
> >elegant), but gobs of whitespace ("adipose tissue"!) really make it
> >difficult, if only because you are less likely to fit essentially
> >connected sections of code on the one page/ screen.
> >--
> >  Cheers,
> >        Paul B.
> >
>
> Send someone a cool Dynamitemail flashcard greeting!! And get rewarded.
> GO AHEAD! http://cards.dynamitemail.com/index.php3?rid=fc-41