[Q] How far can stack [LIFO] solve do automatic garbage collection and prevent memory leak ?

[Q] How far can stack [LIFO] solve do automatic garbage collection and prevent memory leak ? Because a stack has push and pop, it is able to release and allocate memory. We envisage an exogenous stack which has malloc() associated with a push and free() associated with a pop. The algorithm using

Re: [Q] How far can stack [LIFO] solve do automatic garbage collection and prevent memory leak ?

* Standish P, on 16.08.2010 09:20: [garble garble] Nonsense article We look for an exogenous stack cross-posted to [comp.lang.c], [comp.lang.c++], [comp.theory], [comp.lang.python], [comp.lang.forth]. Please refrain from following up on Standish' article. Cheers, - Alf -- blog

Re: [Q] How far can stack [LIFO] solve do automatic garbage collection and prevent memory leak ?

Standish P, 16.08.2010 09:20: We envisage an exogenous stack which has malloc() associated with a push and free() associated with a pop. What's your use case? Stefan -- http://mail.python.org/mailman/listinfo/python-list

Re: [Q] How far can stack [LIFO] solve do automatic garbage collection and prevent memory leak ?

In message 5fa7b287-0199-4349-ae0d-c34c8461c...@5g2000yqz.googlegroups.com, Standish P wrote: We envisage an exogenous stack which has malloc() associated with a push and free() associated with a pop. Since when are malloc(3) and free(3) exogenous? --