Dave Tweed wrote:
> The other objection that I have with end-of-line comments is that they
> really get in the way when subsequently modifying the code. They require
> constant fiddling and reformatting, and this tends to interrupt the train
> of thought regarding the actual code.

With good comments, you only need to "fiddle" with those attached to
whatever you are changing.  In that case it is a Very Good Thing that you
also need to adjust the comments.  That gives you two chances to catch an
incompatibility in the modification, one from the executable code and one
from the comments.

> Even in those rare situations where
> every line requires a comment, I firmly believe that the comments and code
> should be on separate lines.

I guess we'll just have to disagree on this one.  You're one of the few
people on this list that has had to make substantial modifications to PIC
code I wrote years earlier.  Did you feel the extensive end of line comments
were more of an annoyance or a help in understanding the code in the first
place?


*****************************************************************
Embed Inc, embedded system specialists in Littleton Massachusetts
(978) 742-9014, http://www.embedinc.com

--
http://www.piclist.com hint: The list server can filter out subtopics
(like ads or off topics) for you. See http://www.piclist.com/#topics