From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: SRFI-88-style keywords
Date: Tue, 15 Apr 2008 20:56:29 +0200 [thread overview]
Message-ID: <87lk3fgd5u.fsf@gnu.org> (raw)
In-Reply-To: 2bc5f8210804151130y670dab16l9dd6db0165053fc3@mail.gmail.com
Hi,
"Julian Graham" <joolean@gmail.com> writes:
>> Now, we should do something about `cond-expand' and `require-extension'.
>> For the former, we should probably look at the current value of
>> `(read-options)', but that requires changing the implementation of
>> `cond-expand'. For the latter, we can provide a dummy module that
>> modifies `read-options' and re-export the needed procedures.
>>
>> Thoughts?
>
> Sorry, what's the context? Is it that those functions read characters
> independent of the default reader?
We want `cond-expand' (SRFI-0) and `require-extension' (SRFI-55) to be
SRFI-88-aware if possible. See what I mean?
Thanks,
Ludo'.
next prev parent reply other threads:[~2008-04-15 18:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-03 0:14 SRFI-88-style keywords Julian Graham
2007-11-03 14:37 ` Ludovic Courtès
2008-04-15 18:08 ` Ludovic Courtès
2008-04-15 18:30 ` Julian Graham
2008-04-15 18:56 ` Ludovic Courtès [this message]
2008-04-26 19:35 ` Ludovic Courtès
2008-04-27 5:31 ` Julian Graham
2008-04-27 11:22 ` Ludovic Courtès
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=87lk3fgd5u.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@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).