>
> > At times, it's not even possible to use C on the smaller ones.
>
> Which times are those?


See below



> > 3 level hardware stack with C?  :)
>
> What does the hardware stack depth have to do with C?  C does not
> mysteriously consume hardware stack levels.


Nothing "mysterious" about it, but C pushes a lot of things onto the stack
in function calls and ISRs.
In some of my ASM ISRs I don't push ANYTHING because it's not necessary.
When you only have a three word hardware stack, I don't even think it's
possible to use C, is it?



> > Overlapping buffer spaces in a small processor?  Someone check me if I'm
> > wrong but I don't think C will let you do that, and if you did, I doubt
> you
> > could fit the code.
>
> What do you mean by "overlapping buffer spaces?"


Specific case, I needed a rather large input buffer, output buffer, and
stack space.
The sum of the three was about 1.5x the memory in the device.
(of course some will say "use a bigger chip", to which my project manager
would reply " A million times a dime pays your salary for a year, write
better code!"

By overlapping, I mean that I put data into the input buffer at the
beginning of the process, and as I fill up the output buffer, I start using
space that was originally used as input buffer.   I also at some times
needed deep stack space, which overlapped either the in or out, I forget
which, but since I knew exactly what my stack usage was and WHEN, I could
manage that.
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist