Related articles |
---|
[13 earlier articles] |
Re: Ada GC (was about Java VM) darius@phidani.be (Darius Blasband) (1996-02-01) |
Re: Ada GC (was about Java VM) dave@occl-cam.demon.co.uk (Dave Lloyd) (1996-02-02) |
Re: Ada GC (was about Java VM) mg@asp.camb.inmet.com (1996-02-02) |
Re: Ada GC (was about Java VM) boehm@parc.xerox.com (1996-02-02) |
Re: Ada GC (was about Java VM) root@linux_pc.org (1996-02-03) |
Re: Ada GC (was about Java VM) tmb@best.com (1996-02-04) |
Re: Ada GC (was about Java VM) bobduff@world.std.com (1996-02-04) |
Re: Ada GC (was about Java VM) truesoft!sw@uunet.uu.net (1996-02-04) |
Re: Ada GC (was about Java VM) boehm@parc.xerox.com (1996-02-09) |
Re: Ada GC (was about Java VM) eachus@spectre.mitre.org (1996-02-09) |
Re: Ada GC (was about Java VM) kdm@Rational.COM (1996-02-13) |
From: | bobduff@world.std.com (Robert A Duff) |
Newsgroups: | comp.compilers |
Date: | 4 Feb 1996 01:05:57 -0500 |
Organization: | The World Public Access UNIX, Brookline, MA |
References: | 96-01-100 96-02-022 96-02-029 |
Keywords: | Ada, realtime, GC |
Hans Boehm <boehm@parc.xerox.com> wrote:
>Based on measurements by Vincent Delacour, type information would help
>more if you could also know that non-nil pointers always point to the
>garbage collected heap (as might be true in an Ada implementation).
Actually, Ada 95 allows pointers into the stack. However any variable
that might be pointed at in that way has to be explicitly declared
"aliased". So it might make sense for aliased variables to have extra
garbage-collection dope.
>But this isn't free. It typically forces significant numbers of
>constants, etc. to be copied to the heap, solely to preserve this
>invariant.
Why copy them to the heap? Why not just mark them so they are
recognizable at run time?
>And one more nit: Ada is type secure only in the absence of explicit
>deallocation.
Yes, and a bunch of other low-level features!
- Bob
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.