From: Duncan Mak <duncanmak@gmail.com>
To: Per Bothner <per@bothner.com>
Cc: kawa mailing list <kawa@sourceware.org>
Subject: Re: Using with-syntax
Date: Sat, 03 Mar 2018 04:37:00 -0000 [thread overview]
Message-ID: <CABgWrqqCinYvyBWXRqD7Bn1_rNzzzo6W3yxPU4Yh5Uoqg3rGqg@mail.gmail.com> (raw)
In-Reply-To: <1bd6478e-cd70-09ab-6c45-90008329e11f@bothner.com>
(import (except (kawa base) define-variable)) worked, thanks!
I filed an Issue for (kawa syntax-case) library -
https://gitlab.com/kashell/Kawa/issues/38
Duncan.
On Fri, Mar 2, 2018 at 6:50 PM, Per Bothner <per@bothner.com> wrote:
> On 03/02/2018 03:28 PM, Duncan Mak wrote:
>>
>> Hello,
>>
>> I'm writing some macro code and I make use of with-syntax quite a bit.
>> When I load it in the REPL, it all seems to work, but when I load it
>> as an R7RS library module definition, I run into various issues:
>>
>> 1) If I run it with (import (scheme base)), I fall into a recursive
>> loop inside some rewrite step, and it eventually gives up.
>
>
> Curious.
>
>> 2) If I run it with (import (scheme base) (kawa lib std_syntax)), I
>> seem to see something similar (http://savannah.gnu.org/bugs/?49416
>> says to import std_syntax).
>>
>> 3) If I run it with (import (kawa base)), then things seem to work,
>> but now I can't define my own macro named define-variable.
>
>
> How about:
>
> (import (except (kawa base) define-variable))
>
>> What's the right way to get with-syntax to work?
>
>
> We should probably have a (kawa syntax-case) library.
>
> --
> --Per Bothner
> per@bothner.com http://per.bothner.com/
--
Duncan.
prev parent reply other threads:[~2018-03-03 4:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-02 23:29 Duncan Mak
2018-03-02 23:50 ` Per Bothner
2018-03-03 4:37 ` Duncan Mak [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=CABgWrqqCinYvyBWXRqD7Bn1_rNzzzo6W3yxPU4Yh5Uoqg3rGqg@mail.gmail.com \
--to=duncanmak@gmail.com \
--cc=kawa@sourceware.org \
--cc=per@bothner.com \
/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).