From: Kevin Ryde <user42@zip.com.au>
Cc: guile-user@gnu.org
Subject: Re: Is ice-9/poe.scm broken?
Date: Sat, 13 Aug 2005 10:46:00 +1000 [thread overview]
Message-ID: <87k6iq1x6f.fsf@zip.com.au> (raw)
In-Reply-To: <878xz9a0d4.fsf@zagadka.de> (Marius Vollmer's message of "Thu, 11 Aug 2005 01:33:11 +0300")
Marius Vollmer <mvo@zagadka.de> writes:
>
> Could you try to fix this in 1.6 as well?
I put it in, I think it works.
On the merely dodgy as opposed to broken front, I suspect the hash
function should be using logxor, and that perfect-funcq doesn't need
to work the base-func into the hash, since the hash is private the
each func.
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2005-08-13 0:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-08 15:52 Is ice-9/poe.scm broken? Alan Grover
2005-08-10 1:56 ` Kevin Ryde
2005-08-10 22:33 ` Marius Vollmer
2005-08-13 0:46 ` Kevin Ryde [this message]
2005-08-13 10:50 ` Marius Vollmer
-- strict thread matches above, loose matches on Subject: below --
2005-08-08 21:53 Thien-Thi Nguyen
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=87k6iq1x6f.fsf@zip.com.au \
--to=user42@zip.com.au \
--cc=guile-user@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).