From: Han-Wen Nienhuys <hanwen@xs4all.nl>
Cc: guile-devel@gnu.org
Subject: Re: test for weak + struct bug
Date: Wed, 1 Sep 2004 08:59:34 +0200 [thread overview]
Message-ID: <16693.29526.263810.576064@byrd.xs4all.nl> (raw)
In-Reply-To: <87fz62epf8.fsf@zip.com.au>
user42@zip.com.au writes:
> Han-Wen Nienhuys <hanwen@xs4all.nl> writes:
> >
> > here is a shorter test case for Kevin's bug, in case anyone is
> > interested in adding it to the test suite. The display should be
> > replaced by a suitable check.
>
> Beaut, I added it.
>
> (I don't normally think much of adding a test before a fix, but this
> is pretty fundamental.)
I already fixed the problem in 1.6 CVS. Can you test 1.7 too?
--
Han-Wen Nienhuys | hanwen@xs4all.nl | http://www.xs4all.nl/~hanwen
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2004-09-01 6:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-31 22:11 test for weak + struct bug Han-Wen Nienhuys
2004-09-01 1:41 ` Kevin Ryde
2004-09-01 6:59 ` Han-Wen Nienhuys [this message]
2004-09-01 22:04 ` Kevin Ryde
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=16693.29526.263810.576064@byrd.xs4all.nl \
--to=hanwen@xs4all.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).