unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Han-Wen Nienhuys <hanwen@cs.uu.nl>
Cc: guile-devel@gnu.org
Subject: Re: gen gc
Date: Thu, 18 Jul 2002 18:21:36 +0200	[thread overview]
Message-ID: <15670.60176.837367.704404@meddo.cs.uu.nl> (raw)
In-Reply-To: <Pine.GSO.4.05.10207181754510.2467-100000@sallust.ida.ing.tu-bs.de>

dirk@sallust.ida.ing.tu-bs.de writes:
> > What if I can't?  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. 
> > 
> > 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?
> 
> Look into hash.[ch].  scm_hashq seems to be what you think of.

OK. In that case, how is this handled?  Can we simply disallow plain
cells as hash keys?  Oh wait scm_hasher doesn't use the adress of an
object. Good.


-- 

Han-Wen Nienhuys   |   hanwen@cs.uu.nl    | http://www.cs.uu.nl/~hanwen/


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


  reply	other threads:[~2002-07-18 16:21 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 [this message]
2002-07-19 22:55     ` Marius Vollmer
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=15670.60176.837367.704404@meddo.cs.uu.nl \
    --to=hanwen@cs.uu.nl \
    --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).