From: Damien MATTEI <damien.mattei@oca.eu>
To: kawa@sourceware.org
Subject: Re: Reader handling of the @ character
Date: Tue, 30 Jun 2020 00:52:40 +0200 [thread overview]
Message-ID: <0e509794-80b0-e340-3f05-67ea146e5d00@oca.eu> (raw)
In-Reply-To: <ce65797d-157b-f0c3-61ba-544d9873b728@bothner.com>
thanks,
my mail was intend to be in the mailing list.
Le 29/06/2020 à 16:05, Per Bothner a écrit :
> On 6/28/20 8:04 PM, Per Bothner wrote:
>> This seems to work:
>>
>> (define-syntax test
>> (syntax-rules (|@|)
>> ((test @ x y z) (list x y z))))
>>
>> The --r7rs flag also works.
>>
>
> In private email I was asked about |@| and --r7rs.
>
> The slice operator
> @expression
> is converted by the Kawa reader into:
> ($splice$ expression)
>
> The vertical bars in |@| makes @ into a regular
> symbol and disables the special treatment of the @ character.
>
> The --r7rs command-line flag disables Kawa extensions that
> conflict with strict R7RS compatibility:
>
> https://www.gnu.org/software/kawa/Options.html#Options-for-language-selection
>
next prev parent reply other threads:[~2020-06-29 22:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 1:44 Duncan Mak
2020-06-29 3:04 ` Per Bothner
2020-06-29 14:05 ` Per Bothner
2020-06-29 22:52 ` Damien MATTEI [this message]
2020-06-29 22:56 ` Per Bothner
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=0e509794-80b0-e340-3f05-67ea146e5d00@oca.eu \
--to=damien.mattei@oca.eu \
--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).