From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: r6rs incompatibilities
Date: Wed, 26 May 2010 18:43:45 +0200 [thread overview]
Message-ID: <87pr0ipq9q.fsf@gnu.org> (raw)
In-Reply-To: m3ocg2u7bh.fsf@pobox.com
Hi,
Andy Wingo <wingo@pobox.com> writes:
> On Wed 26 May 2010 15:02, Julian Graham <joolean@gmail.com> writes:
>
>>>> We could make this more general, as the r7 committees are wont to do: if
>>>> #! is followed by whitespace or /, then read as a block comment;
>>>> otherwise read one token. In our case, we would read #!foo as #:foo. I
>>>> don't think this change would affect anyone. What do you think?
>>>
>>> Note that there are a couple of other #! constructs being considered for
>>> scheme 7, for example to control case folding. It seems more or less
>>> sensible. Perhaps we should read these as directives, and not as datums
>>> at all.
>>>
>>> There is also the possibility of introducing a reader option for this
>>> behavior.
>>
>> Any chance we could go with my (admittedly sloppy) approach (or
>> something equally as quick) in the short term, and then, as they say
>> in the 'biz, "iterate?" The above sounds sweet, but it seems like
>> it'd make more sense to tackle those things post-2.0.
>
> Heh, sure. But don't make it return SCM_UNSPECIFIED, please; make it
> treat #!r6rs as a comment. See
> http://www.r6rs.org/final/html/r6rs/r6rs-Z-H-7.html#node_sec_4.2.3.
Functions that read comments all return ‘SCM_UNSPECIFIED’, which allows
them to be distinguished by the main loop.
Thanks,
Ludo’.
next prev parent reply other threads:[~2010-05-26 16:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-21 9:54 r6rs incompatibilities Andy Wingo
2010-05-21 12:47 ` Julian Graham
2010-05-21 17:15 ` Andy Wingo
2010-05-23 15:35 ` Julian Graham
2010-05-23 16:02 ` Mike Gran
2010-05-23 17:24 ` Julian Graham
2010-05-23 20:52 ` Andy Wingo
2010-05-23 21:26 ` Andy Wingo
2010-05-26 13:02 ` Julian Graham
2010-05-26 13:21 ` Andy Wingo
2010-05-26 16:43 ` Ludovic Courtès [this message]
2010-05-27 8:06 ` 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=87pr0ipq9q.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).