> Oh, that's not true.  :)
>=20
> If there's anything we all learned, it's ALWAYS our code.  (or maybe =
our
> hardware design)  :)
>=20
> He who suspects the compiler first has a lot yet to learn.

Suspect the compiler first, no, but I have had very odd results (way =
back when) using MSVC 1.52...  I found that the optimizer deemed my =
variable initialization as useless, as well as setting a couple of state =
variables... worked fine in debug, failed in production.  Disabled =
compiler optimizations in production build, and it worked like a charm  =
: ) =20

Sometimes we are NOT paranoid, and it IS the compiler  ; )

('course that was C, not assembly, as most simple PIC programs...)

Steve

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