From: Mikael Djurfeldt <djurfeldt@nada.kth.se>
Cc: guile-devel@gnu.org
Subject: Re: Recent change to syncase.scm
Date: Fri, 07 Feb 2003 08:01:28 +0100 [thread overview]
Message-ID: <xy7el6k377b.fsf@nada.kth.se> (raw)
In-Reply-To: <87vfzw3eyo.fsf@raven.i.defaultvalue.org> (Rob Browning's message of "Thu, 06 Feb 2003 22:13:51 -0600")
Rob Browning <rlb@defaultvalue.org> writes:
> Mikael Djurfeldt <mdj@kvast.blakulla.net> writes:
>
>> I've enabled Guile macro macro expansion in syntax-case macro
>> expansion. This means that, for the first time, Guile macros and
>> syntax-case macros should play reasonably well together.
>>
>> One of the good effects is that goops code now can use syntax-case
>> macros.
>
> Hmm, I wonder if this means that hobbit might be closer to working
> again. One of the big issues last time I was playing with it was that
> there was no way to get all macros "fully expanded" before passing
> them to hobbit.
This is true, although there are some caveats: The syntax-case macro
expansion code does not expand macros of type "syntax" (acros). While
this would be easy to do, it is not meaningful since acros should be
evaluated during evaluation-time. Also, macros which depend on the
detailed representation of the environment will fail.
I suggest you have a look at the expansion code in syncase.scm. It's
quite simple. It basically only extracts the transformer and calls
it.
M
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2003-02-07 7:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-16 12:01 Recent change to syncase.scm Mikael Djurfeldt
2003-01-16 12:41 ` Mikael Djurfeldt
2003-02-07 4:13 ` Rob Browning
2003-02-07 7:01 ` Mikael Djurfeldt [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
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=xy7el6k377b.fsf@nada.kth.se \
--to=djurfeldt@nada.kth.se \
--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).