From: Andy Wingo <wingo@pobox.com>
To: Tristan Colgate <tcolgate@gmail.com>
Cc: guile-devel@gnu.org
Subject: Re: defmacro* and defmacro*-public in master
Date: Mon, 28 Dec 2009 12:05:14 +0100 [thread overview]
Message-ID: <m3r5qfqryt.fsf@pobox.com> (raw)
In-Reply-To: <2e6d10880912150915vc853f8eme1535b8aa5504aab@mail.gmail.com> (Tristan Colgate's message of "Tue, 15 Dec 2009 17:15:03 +0000")
Hi Tristan,
On Tue 15 Dec 2009 18:15, Tristan Colgate <tcolgate@gmail.com> writes:
> Are defmacro* and friends supposed to work in current master?
Yes, they are. But indeed, they weren't working. Thanks for the report,
I have pushed a fix to current master.
> Also, out of interest, is there such a thing as define*-syntax?
No, there is not; though you could build one.
> Is it possible to have docstrings for macros?
Yes, macros can have docstrings. For defmacros, docstrings go in the
same place they would go if it were a function definition.
For syntax-case expressions, the docstring goes with the syntax
transformer:
(define-syntax foo
(lambda (x)
"docs"
(syntax-case x ....)))
Syntax-rules macros currently can't have any docs. We could change that,
but as it would be a nonstandard extension anyway, you're probably
better off using syntax-case.
> doing something like (help macroname) seems to break anyway
Ah, here you have found another bug, I think. I was going to add a
hack-around to (ice-9 documentation) to fix this, but it's probably
better to attack the root, in macros.c.
Cheers,
Andy
--
http://wingolog.org/
prev parent reply other threads:[~2009-12-28 11:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-15 17:15 defmacro* and defmacro*-public in master Tristan Colgate
2009-12-18 13:27 ` Tristan Colgate
2009-12-28 11:05 ` 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=m3r5qfqryt.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=tcolgate@gmail.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).