From: Rob Browning <rlb@defaultvalue.org>
Subject: Re: Switching to a SRFI-45 compliant force/delay.
Date: Sun, 10 Sep 2006 18:33:32 -0700 [thread overview]
Message-ID: <87ac57jifn.fsf@raven.defaultvalue.org> (raw)
In-Reply-To: <87zmd71b0l.fsf@zip.com.au> (Kevin Ryde's message of "Mon, 11 Sep 2006 10:51:06 +1000")
Kevin Ryde <user42@zip.com.au> writes:
> I remember I thought it could go in C in the core nicely enough, or at
> least just extending `force' in the core and leaving the actual
> `eager' to the srfi module perhaps. I don't remember the details
> though, except it might be nice to lose the mutexes at the same time
> :), for speed and size.
>
> http://lists.gnu.org/archive/html/guile-devel/2005-12/msg00050.html
Wow, I had forgotten that discussion.
In any case, I'm not opposed to putting it in C, and I'm also probably
not opposed to dropping the mutexes and just documenting that if you
want sensible results, you need to add a mutex when appropriate.
However, we'd have to be very careful that the C code has identical
semantics to the srfi-45 code, which is somewhat tricky. It may well
be that the code you posted back then will work fine, but I haven't
looked it it carefully enough to be able to be sure one way or the
other.
Of course I suppose we might also be able to just switch to the Scheme
code (plus or minus the mutexes) and plan to migrate to C later.
I'd also like to have all the srfi-45 tests automated, though many of
them are of the format '"this" should execute in bounded space'. I
suppose we could track that via (gc-stats).
--
Rob Browning
rlb @defaultvalue.org and @debian.org; previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2006-09-11 1:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-10 23:24 Switching to a SRFI-45 compliant force/delay Rob Browning
2006-09-11 0:51 ` Kevin Ryde
2006-09-11 1:33 ` Rob Browning [this message]
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=87ac57jifn.fsf@raven.defaultvalue.org \
--to=rlb@defaultvalue.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).