I wonder, and would like somebody to explain, how you can still get bugs
from a C compiler that is years old...  we are not talking about a huge
software platform.  Is this some kind of beta test software?   I never
get any compiling error from the assembler compilers I use for years,
not a single one, so I think it is a steady and fully debugged software.
I only feel confortable working with a screw driver that still to be a
screw driver doesn't matter what.

About C vs Asm, this is a life long discussion thread, the same as
discuss about "what is better to get drunk, beer or vodka?"
C   = Vodka
Asm = Beer

C is faster to write, or vodka to get drunk.
ASM you know exactly what you are doing, and few glasses of beer don't
knock you down so easily.

If you are a good software writer, or a experient drinker, you will
enjoy C as well ASM (beer or vodka) in the same fashion, your final
product will be good in anycase, instead of getting drunk the
experienced drinker would enjoy each sip.

C definetely use more code space than Assembler (for me at least).

Regarding debugging ASM or C, I personally can read (and understand) ASM
source code much faster than C (that requires much more attention to the
more detailed source lines).

In assembler you can optimize better the processor features, memory
space, etc, even that I heard about new C compilers that can do almost
the same.

As I already said before, the final touch:  We made money in assembler
development time, and our wifes spend it in C development time.

In doubt, my personal recomendation is; Learn ASM and C, you will enjoy
both and will find out when and how you should use one or another.

Wagner Lipnharski
Orlando, Florida
http://www.ustr.net


"Dipperstein, Michael" wrote:
>
> > -----Original Message-----
> > From: John Orhan [mailto:JOrhan@edm.com.au]
> > Sent: Tuesday, April 11, 2000 4:58 PM
> > To: PICLIST@mitvma.mit.edu
> > Subject: Re: Question: C vs Asm
> >
> >
> > Hi there,
> > I am wondering if 'c' gives as much versatility ( in terms of embedded
> > multi-tasking ) as assembler. Can 'c' not do things only
> > sequentially? Also
> > there is the question of how compact the assembly code turns
> > out for a 'c'
> > compiled application.
> >
> >                                 John
>
> In C you have just as much control over the order of execution of instructions
> that you do when you code directly in assembly.  Multi-tasking in C is just as
> easy to do as multi-tasking in assembly.
>
> There are only two real drawbacks that I see to using C:
> - Sometimes it is possible to save a few instructions using hand optimized
> assembly vs. machine optimized C.
> - Sometimes I have to contend with compiler errors (which the Hi-Tech people
> have been quick to fix) in addition to my own errors.
>
> The pluses are:
> - I can write the code quicker.
> - The compiler catches some of my errors for me.
> - It's easier to debug by visual inspection.
>
> I have no concrete data on any of these claims, so the management types looking
> for raw data will have to look elsewhere.
>
> -Mike