Related articles |
---|
Lots of things are happening with ACM TOPLAS toplas@cs.umd.edu (1997-03-31) |
gawk memory leak [was Re: Lots of things are happening with ACM TOPLAS arnold@mathcs.emory.edu (1997-04-02) |
Re: gawk memory leak albaugh@agames.com (1997-04-03) |
Re: gawk memory leak stuart@cosc.canterbury.ac.nz (stuart(yeates)) (1997-04-06) |
Re: gawk memory leak bobduff@world.std.com (1997-04-06) |
Re: gawk memory leak max@gac.edu (Max Hailperin) (1997-04-06) |
Re: gawk memory leak hbaker@netcom.com (1997-04-07) |
Re: gawk memory leak cyber_surfer@wildcard.demon.co.uk (1997-04-07) |
Re: gawk memory leak bobduff@world.std.com (1997-04-07) |
Re: gawk memory leak clark@quarry.zk3.dec.com (1997-04-07) |
Re: gawk memory leak arnold@mathcs.emory.edu (1997-04-08) |
Re: gawk memory leak bobduff@world.std.com (1997-04-11) |
Re: gawk memory leak marssaxman@sprynet.com.antispam (1997-04-11) |
Re: gawk memory leak chase@naturalbridge.com (David Chase) (1997-04-11) |
[1 later articles] |
From: | cyber_surfer@wildcard.demon.co.uk (Cyber Surfer) |
Newsgroups: | comp.compilers |
Date: | 7 Apr 1997 15:02:01 -0400 |
Organization: | The Wildcard Killer Butterfly Breeding Ground |
References: | 97-03-165 97-04-020 97-04-022 97-04-040 |
Keywords: | GC, storage |
max@gac.edu uttered these wise words...
> So, no garbage collection doesn't solve the memory leak problem by
> itself, in the sense of without thought, but it isn't just a matter of
> making leaks less common (and premature deallocations/reallocations
> impossible). Instead, it is a matter of making the reasoning much
> easier that it takes to make the leaks go away entirely, as opposed to
> just becoming less common.
I've quoted text from this article in my GC page,
<URL:http://www.wildcard.demon.co.uk/dev/gc.html>
Thanks.
--
<URL:http://www.wildcard.demon.co.uk/>
Martin Rodgers | Programmer and Information Broker | London, UK
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.