> I have just a question to "C" compilers producers:
>
> Your PIC C Compiler program source file is written in C language also,
> correct?  What if, this compiler of the compiler has bugs and generates
> some holes in the PIC C Compiler?  According to some piclisters here, it
> is a fact that *every* C compiler has bugs, alive and identified, or
> hidden and avid to use its fangs over your PIC, so, how can you live in
> such tension of being possibly assaulted by a terrible ghost of despair
> at 2am needing to have the code working for a 9am product presentation?

I worked for a space product (robotic arm for the space station). Our
answer to this problem was that we had to test untill we were satisfied
with the functionality of the final product. We were in the 'fortunate'
situation that
- the CPU was new
- hence the compile was new (never mind the compiler used to produce the
compiler)
- the computer hardware was new
- and of course our specs and the software written to these specs was new

so the answer is: testing, testing, testing, testing, testing, ....

Wouter