> I need your opinion in the case of battle with the software QA
department.
> They are saying GOTO in C not acceptable.
> I checked the books, some of them said no, some of them saying in some
> places there is a use for GOTO.
> 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.

Rules are good but only when a reasonable mechanism exists to decide about
(well motivated) requests to deviate. Most quality standards have such a
mechanism (often called waiver). For a QA department the best motivation
for deviation should be that in some cases (often extreme timing
requirements) the quality can be enhanced (instead of lowered) by using
goto (or inline assembly!). And of course the argument that it is otherwise
impossible should be really convincing, but only if it is really true.

Wouter

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