From: Per Bothner <per@bothner.com>
To: Sudarshan S Chawathe <chaw@eip10.org>, kawa <kawa@sourceware.org>
Subject: Re: SRFI 147 sample implementation and Kawa
Date: Thu, 02 Mar 2017 00:39:00 -0000 [thread overview]
Message-ID: <b57b02c1-1c3a-5d49-faa1-6a139ee9c10d@bothner.com> (raw)
In-Reply-To: <6555.1488413456@vereq.eip10.org>
On 03/01/2017 04:10 PM, Sudarshan S Chawathe wrote:
> When I try testing the sample implementation for SRFI 147 with Kawa I
> get errors (below).
>
> I have not looked at the SRFI implementation carefully so I do not know
> whether the problem is with the implementation or Kawa,
Could be neither or both. The implementation of Scheme hygienic macros is
fairly complicated, and if you push the limits, things may break.
> but I thought
> I'd mention it here. (A similar test with chibi-scheme works, though.)
I think is a case where you have to dig into the Kawa implementation of
macros, and add the desired SRFI-147 functionality. Having it be an add-on
will be fragile, at best, I suspect.
--
--Per Bothner
per@bothner.com http://per.bothner.com/
prev parent reply other threads:[~2017-03-02 0:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-02 0:11 Sudarshan S Chawathe
2017-03-02 0:39 ` 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=b57b02c1-1c3a-5d49-faa1-6a139ee9c10d@bothner.com \
--to=per@bothner.com \
--cc=chaw@eip10.org \
--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).