When optimization is an issue, you can incorporate embedded assembler into your C program as needed.

bcd

-----Original Message-----
From:   Dipperstein, Michael [SMTP:mdippers@HARRIS.COM]
Sent:   Tuesday, April 11, 2000 5:17 PM
To:     PICLIST@MITVMA.MIT.EDU
Subject:        Re: Question: C vs Asm

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