From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: [Guile-commits] GNU Guile branch, syncase-in-boot-9, updated. 3d5f3091e100550052abc698e980b3e86cc01b65
Date: Thu, 30 Apr 2009 12:57:10 +0200 [thread overview]
Message-ID: <m3y6ti2yux.fsf@pobox.com> (raw)
In-Reply-To: <87y6ti1ljk.fsf@gnu.org> ("Ludovic Courtès"'s message of "Thu, 30 Apr 2009 12:30:07 +0200")
Hi,
On Thu 30 Apr 2009 12:30, ludo@gnu.org (Ludovic Courtès) writes:
> "Andy Wingo" <wingo@pobox.com> writes:
>
>> * libguile/macros.h: Add API for syncase macros.
>
> Perhaps these should be made `SCM_INTERNAL'?
The functions should probably be public, as they are public to Scheme.
The bit-twiddlings should either be left as-is, or pulled into
macros.c -- but there is already some bit-twiddling that's public.
>> +SCM_DEFINE (scm_make_syncase_macro, "make-syncase-macro", 2, 0, 0,
>> + (SCM type, SCM binding),
>> + "Return a @dfn{macro} that requires expansion by syntax-case.\n"
>
> [...]
>
>> +SCM_DEFINE (scm_make_extended_syncase_macro, "make-extended-syncase-macro", 3, 0, 0,
>> + (SCM m, SCM type, SCM binding),
>> + "Extend a core macro @var{m} with a syntax-case binding.")
>
> Can you explain how it works? Having a SMOB type for `syntax-case'
> macros seems counter-intuitive to me. :-)
It's the same smob type as normal macros, but a different macro type.
Have another look :)
Andy
--
http://wingolog.org/
prev parent reply other threads:[~2009-04-30 10:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1LzFO3-0008J4-56@cvs.savannah.gnu.org>
2009-04-30 10:30 ` [Guile-commits] GNU Guile branch, syncase-in-boot-9, updated. 3d5f3091e100550052abc698e980b3e86cc01b65 Ludovic Courtès
2009-04-30 10:57 ` Andy Wingo [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=m3y6ti2yux.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=ludo@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).