> I don't think the world cares much how you call it - it is commonly
> called "stactic stack allocation" or something similar. In the absence
> of re-entry and recursion it is )for the user)m indistinguishable from a
> "real" stack.

As you can see in C18 it is not only me who calls this as an overlay :-) -
And no, it was not me who designed C18 :-) Anyway, I would not mind calling
it as static or pseudo stack but I do think that this naming is misleading.

Anyway,



On Thu, Oct 23, 2008 at 7:12 PM, Wouter van Ooijen <wouter@voti.nl> wrote:

> Tamas Rudnai wrote:
> >> I mistyped, it should be "static stack". That's a stack that is
> >> pre-calculated at compile time, so it can use fixed adresses at run
> >> time. But this does not permit recursion or reentrancy.
> >
> > That is what I call overlayed memory usage - that is not even a stack. In
> my
> > opinion it is much better what C18 do, it does not try to figure out what
> I
> > want, but I can trigger this option by the storage specifier 'overlay':
>
> I don't think the world cares much how you call it - it is commonly
> called "stactic stack allocation" or something similar. In the absence
> of re-entry and recursion it is )for the user)m indistinguishable from a
> "real" stack.
>
> --
>
> Wouter van Ooijen
>
> -- -------------------------------------------
> Van Ooijen Technische Informatica: www.voti.nl
> consultancy, development, PICmicro products
> docent Hogeschool van Utrecht: www.voti.nl/hvu
>
> --
> http://www.piclist.com PIC/SX FAQ & list archive
> View/change your membership options at
> http://mailman.mit.edu/mailman/listinfo/piclist
>



-- 
Rudonix DoubleSaver
http://www.rudonix.com
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist