AVR-Chat

> A very common problem is where one routine messes with another's variables.
> Either by direct reference, or indexed as My_Ram+5 accidentally stepping on
> Your_Ram
The trouble here is the concept of "ownership" of the variables (This is
clearly defined and controlled in high level OOP languages, but not in
assembler). The same problem arises in detecting corruption of variables
by interrupt handlers - it alters a register, but should the ISR have
preserved the register, or does it "own" the register and therefore the
action is legitimate?

> > > I wrote one application where I deliberately overlapped my input buffer,
> > > output buffer, and stack space in SRAM, but with careful design, it was
> > fine.
> >*Very* careful I imagine. I'd just use the next chip up, with more RAM
> 
> What 8 pin chip, has more ram than the 2343?
Don't know, but I'd be looking for one! 'twas a general comment that
comtemplating techniques like that is a dead giveaway that you've
outgrown your hardware capacity.

Rob