Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!TAURUS.BITNET!zifrony
From: zifrony@TAURUS.BITNET
Newsgroups: comp.misc
Subject: Re: Program Errors and developement environment
Summary: One line comments
Message-ID: <1001@taurus.BITNET>
Date: 27 Mar 89 18:35:42 GMT
References: <4352@enea.se> <2950@hound.UUCP> <3998@ttidca.TTI.COM>
Sender: daemon@ucbvax.BERKELEY.EDU
Reply-To: <zifrony%TAURUS.BITNET@CUNYVM.CUNY.EDU>
Organization: Tel-Aviv Univesity Math and CS school, Israel
Lines: 31


Maybe the answer is the languages having "till the end of the line" comments,
such as Ada, PostScript, most Assembly languages, FORTRAN, etc.
This way, the programmer cannot delete code by mistake.

The loss of flexibility in the places comments could come seems to me
minor to the gain in security.  Most of the comments I ran to during my
professional programming life were either a comment block (which this comment
style suits just fine), or comments at the end of the line, which can be
acheived using this commenting style as well.

This commenting style can be immitated by the structured-comments languages
such as Pascal and C:

Use a special line to start a comment block, precede each line with '*', and
end it with a special line too.  e.g.:

/*
 *   blah blah blah
 *
*/

End of the line comments should never be written to span over line
boundaries.  use another comment separator-pair if it is too long.

Keep this up, and your commenting problems will disappear.

Doron  Zifrony   zifrony%taurus.bitnet@cunyvm.cuny.edu   or
Msc.   student   zifrony@Math.Tau.Ac.IL
Tel Aviv Univ.
Israel