From: ludo@gnu.org (Ludovic Courtès)
To: Mike Gran <spk121@yahoo.com>
Cc: guile-devel@gnu.org
Subject: Re: Merging R6RS libraries?
Date: Tue, 30 Mar 2010 23:53:53 +0200 [thread overview]
Message-ID: <878w99v5la.fsf@gnu.org> (raw)
In-Reply-To: <828590.29092.qm@web37903.mail.mud.yahoo.com> (Mike Gran's message of "Tue, 30 Mar 2010 10:59:16 -0700 (PDT)")
Hi Mike,
Mike Gran <spk121@yahoo.com> writes:
> Ludo wrote:
>
>> - Do you plan to work on the remaining parts, in
>> particular the dreaded (to me) ‘(rnrs io ports)’?
>> :-)
>
> I've been thinking a little about how (rnrs io ports) might
> be accomplished. If no one has been working on it, I could
> lay out some of my opinions and something of a plan.
Yes, please!
Thanks,
Ludo’.
prev parent reply other threads:[~2010-03-30 21:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-29 21:27 Merging R6RS libraries? Ludovic Courtès
2010-03-29 23:06 ` Julian Graham
2010-04-11 3:50 ` Julian Graham
2010-04-11 21:49 ` Andy Wingo
2010-05-21 2:04 ` Julian Graham
2010-05-22 13:51 ` Ludovic Courtès
2010-03-30 17:59 ` Mike Gran
2010-03-30 21:53 ` Ludovic Courtès [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=878w99v5la.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@gnu.org \
--cc=spk121@yahoo.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).