Olin Lathrop wrote:

> Isaac Marino Bavaresco wrote:
>>> I have found completely the opposite.  At least with C18, I can
>>> rarely get MPLAB to show me local variables, step cleanly from one
>>> source line to the next, etc.  Debugging the C18 parts of a mixed
>>> C18/MPASM project is *much* harder than the MPASM parts.
>>
>> MPLAB is indeed buggy, but it is not the only available option.
> 
> I'm not sure if this is due to bugs or just how it works or the kind
> of information C18 passes to the COD file via the linker. 
> 
>> With a good IDE and debug Tool, all the advantages of C pop to the
>> eyes.
> 
> I agree that the problems debugging C18 with MPLAB are not inherent
> to C, but that's nonetheless what I have to deal with.

How's your Pascal compiler doing in this respect? Can you step through
the source code, view variable values? Is it any better than C18? If
not, is this an argument against Pascal?

FWIW (and this of course applies only to whoever thinks it applies :),
for a pro it should be possible to buy a tool chain that works. If
MPLAB/C18 doesn't, I'd get one that does.

There are people who think that MPLAB isn't well suited for programming
chips. There are also people who think that MPLAB isn't well suited for
programming -- and both may have a point, or may not :)

Gerhard
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist