> My practice said, when writing code for PIC especially fast operation with
> nested loops
> ( like decoding noise RF Manchester transmission at 100 kbit/s ) GOTO is
> absolutely necessary.

I think that programming for the PIC and programming for a large general
purpose computer are different enough to warrant different rules.  As
someone mentioned before, the stack limit could be reason to justify a
goto.

I have a program that I am planning on migrating to a 2-deep stack PIC,
and I can assure you that I use gotos without feeling bad about it.

So, if they are trying to apply a general rule to a "special" (i.e. pic ==
special) case, maybe they could reconsider.

-Steve

--
http://www.piclist.com#nomail Going offline? Don't AutoReply us!
use mailto:listserv@mitvma.mit.edu?body=SET%20PICList%20DIGEST