Tamas Rudnai wrote:
>> > Use JAL (or  C) for 10F/12F/16F/18F and write reusable libraries with
>> > comments as if you are trying to understand someone else's code.
>>
>> Or you can forego the comments and write self-documenting code. :)
>>
>
> There is no such as self-documented code -- only lazy programmers :-)

Your comment seems to imply that there are other kinds of programmers.


> Comments are telling you what the code meant to do -- as opposed to code,
> which tells what did you (or somebody) do. So if you compare the two, you
> would see if you (or others) did it correctly.

Deja vu -- I'm sure we've done this debate already. :)

In a nutshell, if you apply the "loose coupling/tight cohesion" principle, 
and use appropriate names for variables and functions, you can eliminate the 
need for most comments.

Whenever I see heavy use of comments, it is usually a good indication of 
poorly written code.

[FLAME SHIELD ON]

Vitaliy 

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