From: ludo@gnu.org (Ludovic Courtès)
To: Andy Wingo <wingo@pobox.com>
Cc: guile-devel@gnu.org
Subject: Re: thoughts on ports
Date: Sun, 20 Jan 2013 23:11:01 +0100 [thread overview]
Message-ID: <87libnqzd6.fsf@gnu.org> (raw)
In-Reply-To: <874niba9mk.fsf@pobox.com> (Andy Wingo's message of "Sun, 20 Jan 2013 21:21:23 +0100")
Andy Wingo <wingo@pobox.com> skribis:
> The goal was to be able to provide Scheme functions that operate on
> ports, but that can suspend the operation via an abort-to-prompt if it
> will block. This can only be done if we are not recursing through C.
> Exposing the fundamental buffers lets port operations to be implemented
> in Scheme (while also allowing the C implementation).
OK, I see, and it makes sense to me.
Ludo’.
next prev parent reply other threads:[~2013-01-20 22:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-08 20:21 thoughts on ports Andy Wingo
2012-04-09 19:15 ` Mike Gran
2012-04-09 20:21 ` Noah Lavine
2012-04-10 22:11 ` Ludovic Courtès
2013-01-17 14:40 ` Andy Wingo
2013-01-18 21:27 ` Ludovic Courtès
2013-01-20 20:21 ` Andy Wingo
2013-01-20 22:11 ` Ludovic Courtès [this message]
2012-04-11 18:36 ` Mark H Weaver
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=87libnqzd6.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@gnu.org \
--cc=wingo@pobox.com \
/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).