> Has someone on this PICList posted standards for coding and commenting?
> I mean, how many tabs to indent for code and comments, what to
> capitalize, etc.

Ha, ha.  Posting standards isn't the problem, getting others to follow
them is.  Everyone naturally has their own idea of how things should be
indented, capitalized, etc.  As for commenting, it's a struggle just to
get people to do it at all.  (Although I've noticed even Andrew Warren has
recently started commenting the code snippets he posts.  Thanks, Andy.
Maybe there is hope.)

For whatever it's worth, I put labels in column 1 (the assembler requires
that), opcodes in column 10, operands starting in column 18, and end of
line comments starting in column 30.  I sometimes receive code from other
places, and it's usually a mess (why else would someone hire a consultant
to "fix" it?).  For my sanity, I've created a program called ASPIC_FIX
that fixes arbitrary messy alignment to the above values.  It also
eliminates tabs and only uses hard spaces for formatting in the output
file.  ASPIC_FIX is part of my PIC development environment, which you can
download for free.  See http://www.embedinc.com/pic.

As for capitalization, I write everything lower case because something is
a lot quicker to type if you don't have to keep hitting CAPS LOCK or
holding down the SHIFT key.


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

--
http://www.piclist.com#nomail Going offline? Don't AutoReply us!
email listserv@mitvma.mit.edu with SET PICList DIGEST in the body