On Tue, Jun 15, 2010 at 2:16 AM, Vitaliy wrote: > 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. > Recent years I rarely can see other kinds of programmers :-) > Deja vu -- I'm sure we've done this debate already. :) > Do not worry, that was only adjusting the Matrix :-) But yes, we have been discussing this 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. > Interesting to see your experience. My observation was the opposite: Whenever a programmer is lazy to comment, also lazy to write good and self-documenting code. Tamas > > [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 > -- int main() { char *a,*s,*q; printf(s="int main() { char *a,*s,*q; printf(s=%s%s%s, q=%s%s%s%s,s,q,q,a=%s%s%s%s,q,q,q,a,a,q); }", q="\"",s,q,q,a="\\",q,q,q,a,a,q); } -- http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist