From: Kevin Ryde <user42@zip.com.au>
Cc: guile-devel@gnu.org
Subject: Re: 1.8
Date: Sat, 24 Dec 2005 11:59:48 +1100 [thread overview]
Message-ID: <87irtf2ttn.fsf@zip.com.au> (raw)
In-Reply-To: <1135352415.4312.56.camel@localhost.localdomain> (Andy Wingo's message of "Fri, 23 Dec 2005 10:40:15 -0500")
Andy Wingo <wingo@pobox.com> writes:
>
> My guess:
4) Under debug-cell-accesses, goops.test is throwing
Non-pair accessed with SCM_C[AD]R: `#<<class> <foo> b7baf270>'
but I don't know if that's benign in practice.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2005-12-24 0:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-20 16:32 GC improvements Ludovic Courtès
2005-12-23 11:29 ` Han-Wen Nienhuys
2005-12-23 15:40 ` 1.8 [was: GC improvements] Andy Wingo
2005-12-24 0:59 ` Kevin Ryde [this message]
2006-01-03 10:16 ` GC improvements Ludovic Courtès
2006-01-04 1:03 ` Han-Wen Nienhuys
2006-01-04 16:18 ` Ludovic Courtès
2006-01-05 14:47 ` Ludovic Courtès
2006-01-06 20:22 ` Han-Wen Nienhuys
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=87irtf2ttn.fsf@zip.com.au \
--to=user42@zip.com.au \
--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).