From: Marius Vollmer <mvo@zagadka.ping.de>
Cc: guile-devel@gnu.org
Subject: Re: gen gc
Date: 20 Jul 2002 00:55:00 +0200 [thread overview]
Message-ID: <87k7nrcoqj.fsf@zagadka.ping.de> (raw)
In-Reply-To: <15669.63974.973133.308661@blauw.xs4all.nl>
Han-Wen <hanwen@cs.uu.nl> writes:
> mvo@zagadka.ping.de writes:
>
> > It would be cool if you could fake it. It doesn't need to be the real
> > memory address of the object, just a unique integer.
>
> What if I can't?
Then we can remove object-address. If people need something like it,
we can keep it, but with a different name and the warning that the
address of an object might change over its lifetime.
> Memory cells are going to move around. I don't see a way to generate
> a unique number without making some kind of table for objects
> subjected to object-address.
Yes. But for a deprecation period, this will be good enough, no?
> Btw, I can imagine that internal hash tables might use the address of
> a cell as a source for a hash index. Does that happen anywhere?
Yes, in scm_ihashq and scm_ihashv and maybe elsewhere. There are
techniques to deal with this, I believe...
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-07-19 22:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-17 21:59 gen gc Han-Wen
2002-07-17 22:54 ` Marius Vollmer
2002-07-17 23:12 ` Han-Wen
2002-07-18 12:08 ` Miroslav Silovic
2002-07-18 12:08 ` Han-Wen Nienhuys
2002-07-19 3:59 ` Rob Browning
2002-07-19 9:39 ` Han-Wen
2002-07-19 15:40 ` Rob Browning
2002-07-19 19:07 ` Tom Lord
2002-07-19 21:07 ` Han-Wen Nienhuys
2002-07-19 21:32 ` Rob Browning
2002-07-19 22:33 ` Han-Wen
2002-07-19 23:31 ` Rob Browning
2002-07-19 22:58 ` Marius Vollmer
2002-07-18 16:00 ` Dirk Herrmann
2002-07-18 16:21 ` Han-Wen Nienhuys
2002-07-19 22:55 ` Marius Vollmer [this message]
2002-07-20 8:06 ` Neil Jerram
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k7nrcoqj.fsf@zagadka.ping.de \
--to=mvo@zagadka.ping.de \
--cc=guile-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).