Em 15/6/2010 09:46, Olin Lathrop escreveu:
> Vitaliy wrote:
>   =

>> poorly written code requires a lot of
>> explaining. Well written code requires little or none.
>>     =

> This is where you're wrong.  Well written code may require a little less
> explaining, but no amount of verbose and carefully chosen symbol names can
> provide the kind of information that good comments can.  The two work
> together.  It's not a question of which one is best.
>   =


There are certain cases that I can't imagine how to make fully
self-commenting code:

1) Routines that implement communication protocols, are much easier to
understand with comments that correlate the code statements with what
they do in the protocol, or even embed parts of the protocol
specification into the code.
2) Certain code optimizations make the code very hard to understand and
need a lot of comments to explain how the code works.

Isaac

__________________________________________________
Fale com seus amigos  de gra=E7a com o novo Yahoo! Messenger =

http://br.messenger.yahoo.com/ =


-- =

http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist