unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Rob Browning <rlb@defaultvalue.org>
Cc: Miroslav Silovic <miro@puremagic.com>,
	Marius Vollmer <mvo@zagadka.ping.de>,
	guile-devel@gnu.org
Subject: Re: gen gc
Date: Fri, 19 Jul 2002 10:40:03 -0500	[thread overview]
Message-ID: <87d6tjsp4c.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <15671.56925.864831.996455@blauw.xs4all.nl> (Han-Wen's message of "Fri, 19 Jul 2002 11:39:41 +0200")

Han-Wen <hanwen@cs.uu.nl> writes:

> What do you mean by integer counter?

A unique per-object value taken from a plain old integer sequence.
i.e. the first object is 1, the second is 2, etc.

> The value is only intended for human consumption (i.e. debugging)

OK, that's one thing I wasn't sure of, and given that, I wasn't sure
whether a unique number that's constant across the lifetime of the
object (an integer), or the address (which may change) would be more
useful.  I suppose it depends on what type of debugging you're trying
to do, and of course, the address would be cheaper to provide.

Note though, that if there's not supposed to be a way to look up an
object by its object-address value, then you don't need to store the
values in a hash table mapping to objects or similar.

-- 
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG=1C58 8B2C FB5E 3F64 EA5C  64AE 78FE E5FE F0CB A0AD

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


  reply	other threads:[~2002-07-19 15:40 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 [this message]
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
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=87d6tjsp4c.fsf@raven.i.defaultvalue.org \
    --to=rlb@defaultvalue.org \
    --cc=guile-devel@gnu.org \
    --cc=miro@puremagic.com \
    --cc=mvo@zagadka.ping.de \
    /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).