From Newsgroup: comp.lang.c++
On Mon, 02 Nov 2026 16:51:46 GMT, Charlie Gibbs wrote:
On 2026-11-02, Fred. Zwarts <F.Zwarts@HetNet.nl> wrote:
Op 02.nov.2026 om 10:54 schreef Rosario19:
On Tue, 20 Oct 2026 20:20:39 -0000 (UTC), Lawrence D|+Oliveiro wrote:
On Tue, 20 Oct 2026 15:06:48 -0500, Lynn McGuire wrote:
The key to writing any software is lots of commenting.
A key point about comments is they should explain *why* the code is
the win for comment it is when code explain itself with 0 comment
Code can only explain what it does, what the algorithm is.
Code cannot explain why that algorithm was chosen. That is where
comments are for.
Unfortuately, a lot of people (especially CS weenies) love to
loudly proclaim, "My code is so readable that no comments are
necessary!" (Sometimes they apply this argument to their choice
of programming language as well.) They're usually wrong.
I m not a too much code writer
until now, making some test I can understand and can correct bug on my
code even if not commented enought (but input variable and output
variable of one function are always/ should always be commented). code difficult as printf like functions, malloc, bignum function operators
etc in assembly too.
On others code i suspect it would be difficult for me even if
commented... the indentation and names of variable are one easy way of
comment code (i read that in a book speak on pascal language), without
write one line of comment. Writing always the same type of loop, the
same type of inizialization in the same position, the same names, I
can figure out all soon...
--- Synchronet 3.22a-Linux NewsLink 1.2