> As far as I am concerned, a program should first be written to be
> READABLE, by the original author, and others. Ideally, if you write a
> program, someone else should be able to look at it and understand what
> it does and how it does it. It doesn't matter in which language it is
> written. Programs in assembler can be made very readable; programs in
> the highest, most structured language can be made unreadable. "C" can be
> particularly obscure - it was designed as a concise language, basically
> as a high-level assembler.=20
>=20
> THEN, you can start to look at memory size and performance issues. Any
> deviations from the Principle of Maximum Readability should be carefully
> documented.
>=20
> If you have difficulty describing (in comments) what a piece of code
> does, REWRITE it. If YOUR are having trouble, pity the poor person who
> has to look at it a year from now (that person may be YOU).
>=20
> Programming a PIC is no different from programming a PC, or an IBM
> mainframe. The same principles of programming apply. Because of space
> and time considerations, the PIC code may have to be tweaked.  Even if
> the program is a one-of, it is still good discipline to do it as well as
> you can.

+1

>=20
> My opinion only. Do NOT look at any of MY code to see if I follow my own
> advice :)
>=20

Definitely +1


> --=20
> Larry Bradley =20
> Orleans (Ottawa) Canada=20
>=20

/Ruben


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