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

[John Kelly]

On Tue, 17 Aug 2010 11:53:27 -0700 (PDT), Standish P <stndshp at gmail.com>
wrote:

>Another way to pose my question, as occurred to me presently is to ask
>if a stack is a good abstraction for programming ? Certainly, it is
>the main abstraction in Forth and Postscript and implementable readily
>in C,C++ and I assume python.

>so the name of the game is the same, ie to help the programmer keep
>track of things for writing fault free code without chasing every
>case, easy visualization, easy recall and communication with fellow
>programmers of abstract concepts in terms of real world objects and
>easy modification and code reuse.


"Go is an attempt to combine the ease of programming of an interpreted,
dynamically typed language with the efficiency and safety of a
statically typed, compiled language. It also aims to be modern, with
support for networked and multicore computing"

"To make the stacks small, Go's run-time uses segmented stacks. A newly
minted goroutine is given a few kilobytes, which is almost always
enough. When it isn't, the run-time allocates (and frees) extension
segments automatically"

http://golang.org/doc/go_lang_faq.html



-- 
Web mail, POP3, and SMTP
http://www.beewyz.com/freeaccounts.php