>My major gripes with MPLAB has always the 16-bit code, the clunky
>simulator (although I do use it once in a while), the AWFUL support for
>3rd party compilers -- especially source level debugging in C. Some may
>say it's not realistic to ask Microchip to support 3rd party tools,
>BUT...

I cannot understand why they have not caused the Borland compiler they use,
to produce 32 bit code. Perhaps Microchip have been developing MPLAB on Win
3.1 machines :))

The bits I hate about it are the way a new version breaks previous versions.
Installed one of the 5.6.something releases recently to find that the macro
handling during emulation was broken. Previously when stepping through a
macro, the cursor would sit at the instruction previous to the macro, until
the single step reached the next instruction after the macro. The broken one
would shoot the cursor several instructions previous to the macro, which
could be in the previous subroutine, and had one looking twice to verify
where the code was actually executing.

Also had some strange happenings with attempting to scroll windows. Try to
scroll a source code window, and no matter what one did, the ROM code window
would insist on scrolling, even though it was not the foreground window.

So yes, there are aspects about it that are junk. It is not unreasonable to
expect it to improve as new versions come out, not break existing bits -
that is why people use HLL's, isn't it??? :))

--
http://www.piclist.com hint: The PICList is archived three different
ways.  See http://www.piclist.com/#archives for details.