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

Hugh Aguilar hughaguilar96 at yahoo.com
Wed Aug 25 02:00:14 CEST 2010


On Aug 24, 4:17 pm, Richard Owlett <rowl... at pcnetinc.com> wrote:
> Hugh Aguilar wrote:
> > [SNIP ;]
>
> > The real problem here is that C, Forth and C++ lack automatic garbage
> > collection. If I have a program in which I have to worry about memory
> > leaks (as described above), I would be better off to ignore C, Forth
> > and C++ and just use a language that supports garbage collection. Why
> > should I waste my time carefully freeing up heap space? I will very
> > likely not find everything but yet have a few memory leaks anyway.
>
> IOW Hugh has surpassed GIGO to achieve AGG -
> *A*utomatic*G*arbage*G*eneration ;)

The C programmers reading this are likely wondering why I'm being
attacked. The reason is that Elizabeth Rather has made it clear to
everybody that this is what she wants:
http://groups.google.com/group/comp.lang.forth/browse_thread/thread/c37b473ec4da66f1

Every Forth programmer who aspires to get a job at Forth Inc. is
obliged to attack me. Attacking my software that I posted on the FIG
site is preferred, but personal attacks work too. It is a loyalty
test.



More information about the Python-list mailing list