> And I absolutely abhor line-by-line comments, in assembly
> or any other language. More often than not, they just restate
> what the line of code says without adding any higher-level
> insight as to what the overall intention or functionality is

Could I suggest that this is the author's fault, as a comment
in itself can only be how it's written. I agree that verbose text
(waffle) can make code harder to follow, and prefer a fullish
subroutine title + short paragraph and special commenting
which doesn't, as you say, just put the mnemonics into plain
English. The choice of names for labels, macros and so on
is commenting too and helps make code self-explanatory

--
http://www.piclist.com hint: PICList Posts must start with ONE topic:
[PIC]:,[SX]:,[AVR]: ->uP ONLY! [EE]:,[OT]: ->Other [BUY]:,[AD]: ->Ads