Isaac Marino Bavaresco wrote:
> For some very critical cases the assembly language may be better, but
> if
> the object code fits in the program memory, it doesn't matter if it
> takes 50%, 70% or even 80% of the memory.

It does if it's a high volume project and a cheaper processor could have
been used.

>> 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.

> You appear to be locked to a single vendor and architecture.

This is the *PIC* list.  Yes, I'm talking about PIC development.

>> Then you need to learn to document your code better.  This is not a
>> language issue, but a code discipline and documentation issue, and
>> applies to all languages.  I've seen some horribly obtuse C code.
>> You can make a mess in any language, and you can also write clear
>> code.  Don't blame the language.
>
> Your argument only stands if you assume I document poorly my C code
> and you document your assembly code well.

Yes, since that appears to be the case.

> Just suppose somebody very
> disciplined write and document both the C and assembly code, which one
> is more compact, has less lines of code and is easier to understand?
>
> What if you are studying somebody else's code, isn't it easier to
> understand if it is in a high-level language?

Not necessarily.  It all depends on how logically the project is broken up
and how well documented.  This is largely independent of language.
Unfortunately some languages make it easier to make a mess or write obtuse
code than others, like C, but you can still write good or bad code in any
language.

> Specially if you don't know the architecture?

Obviously for assembler we are assuming familiarity with the architecture.


********************************************************************
Embed Inc, Littleton Massachusetts, http://www.embedinc.com/products
(978) 742-9014.  Gold level PIC consultants since 2000.
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist