AVR-Chat

> I suspect that the general consensus is that if you have a need for
> an extremely efficient ISR (or any function for that matter), you
> can always code it completely in assembly language.  I have done
> this from time to time.  Using mixed C and assembly language gives
> you the "best of both worlds".   You get the benefits of using C for
> most of your application and, where it is needed, you get the
> benefit of highly tuned, hand-crafted assembly language code.

That's what I expect, and having done a lot of ASM in the past, plus
loads of hardware, I'm trying to position myself as a good all-around
embedded systems guy.  While I haven't yet been asked to do anything
that I couldn't do in ASM, and I have done things that wouldn't be
possible in C, it seems that at this point, all potential employers or
clients expect me to know C....

I do see a class of problems that would be intractable in ASM in any
practical sense, but it's just that I haven't yet hit any of that in
real projects that clients or employers have given me so far..

Eventually I see myself writing most of the app in C, and then writing
ISRs and maybe low level drivers and time-critical code in ASM.