From: ludo@gnu.org (Ludovic Courtès)
To: Julian Graham <joolean@gmail.com>
Cc: Andy Wingo <wingo@pobox.com>, guile-user@gnu.org
Subject: Re: srfi-34 and raise
Date: Mon, 07 Jun 2010 12:07:57 +0200 [thread overview]
Message-ID: <87y6erkveq.fsf@gnu.org> (raw)
In-Reply-To: <AANLkTil434ZGLoZhUS3vFM81yXtnRDC3yzad_-ya6qXD@mail.gmail.com> (Julian Graham's message of "Sun, 6 Jun 2010 22:03:13 -0400")
Hi!
Julian Graham <joolean@gmail.com> writes:
>>> There are also many bindings that could be #:replaced in the rnrs
>>> modules.
>>
>> Yes, we should fix that. Perhaps Julian would be willing to do that? :-)
>
> Sure, although the solution that springs to my mind first is to make
> all bindings introduced by R6RS libraries #:replace-ing, via the
> `import' transformer. Objections?
Can you give an example of what you mean?
Thanks,
Ludo’.
next prev parent reply other threads:[~2010-06-07 10:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-04 8:48 srfi-34 and raise Tristan Colgate
2010-06-06 20:09 ` Andy Wingo
2010-06-06 20:47 ` Ludovic Courtès
2010-06-06 22:51 ` Andy Wingo
2010-06-07 2:03 ` Julian Graham
2010-06-07 10:07 ` Ludovic Courtès [this message]
2010-06-07 21:04 ` Andy Wingo
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=87y6erkveq.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-user@gnu.org \
--cc=joolean@gmail.com \
--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).