From: Per Bothner <per@bothner.com>
To: kawa@sourceware.org
Subject: Re: Splicing lists and vectors into argument lists
Date: Mon, 12 May 2014 21:56:00 -0000 [thread overview]
Message-ID: <53714363.3090306@bothner.com> (raw)
In-Reply-To: <m2r441jwoe.fsf@gmail.com>
On 05/10/2014 11:49 AM, Helmut Eller wrote:
> On Sat, May 10 2014, Per Bothner wrote:
>
>> A issue is that initial '@' in a symbol is *not* allowed by R7RS or
>> R6RS. ('@' is a <special subsequent> so is not allowed as an initial
>> character.)
>
> Oh boy. They let you put Unicode chars there but no @. Oh wait, they
> actually say "it is an error for the first character to have a general
> category of Nd, Mc, or Me." But @ belongs to category Po. And again
> they use the meaningless phrase "it is an error" which of course only
> means that it may or may not be allowed by an implementation.
I just noticed the r7rs errata:
http://trac.sacrideo.us/wg/wiki/R7RSSmallErrata
7, In Section 7.1.1, the lexical rule <special initial> incorrectly omits @.
Since (in my reading) r6rs also allows an initial '@', I think it would be
correct for the --r7rs/--r6rs/--r5rs flags to disable the '@' reader
mapping from @EXPR to ($splice$ EXPR). (r5rs doesn't allow an initial '@',
but allowing it would still be a compatible extension, so for simplify
--r5rs behaves the same.)
So I checked in a fix for this:
$ kawa --r7rs
#|kawa:1|# (define @ 3)
#|kawa:2|# (define @2 2)
#|kawa:3|# (+ @ @2)
5
--
--Per Bothner
per@bothner.com http://per.bothner.com/
prev parent reply other threads:[~2014-05-12 21:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-09 16:19 Per Bothner
2014-05-10 7:27 ` Helmut Eller
2014-05-10 16:51 ` Per Bothner
2014-05-10 18:50 ` Helmut Eller
2014-05-12 21:56 ` Per Bothner [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53714363.3090306@bothner.com \
--to=per@bothner.com \
--cc=kawa@sourceware.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).