unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Tristan Colgate <tcolgate@gmail.com>
To: guile-devel@gnu.org
Subject: defmacro* and defmacro*-public in master
Date: Fri, 18 Dec 2009 13:27:38 +0000	[thread overview]
Message-ID: <2e6d10880912180527k3ae5af5aqa2eb0f9bc5719cb5@mail.gmail.com> (raw)
In-Reply-To: <2e6d10880912150915vc853f8eme1535b8aa5504aab@mail.gmail.com>

[I sent this before subscribing but it hasn't turned up so I'm resending now,
sorry if the previous posting reappears some time later]

Hi Guys,

 Are defmacro* and friends supposed to work in current master? I've
got some code that works under 1.8 but fails on master. I checked
the trivial examples in the manual, and sure enough, they fail as well...

scheme@(guile-user)> (use-modules (ice-9 optargs))
scheme@(guile-user)> (defmacro* transmorgify (a #:optional b)
...               (a 1))
ERROR: In procedure sc-expand:
ERROR: source expression failed to match any pattern in (defmacro*
transmorgify (a #:optional b) (a 1))
scheme@(guile-user)>

 None of the unit tests seem to directly cover these macros.

 Also, out of interest, is there such a thing as define*-syntax?

 And, whilst I'm at it, on a probably unrelated matter? Is it
possible to have docstrings for macros? It doesn't
seem unreasonable, but doing something like (help macroname) seems to
break anyway (for relatively obvious
reasons).

 Thanks very much for all the hard work you guys are putting in,

 Cheers

-- 
Tristan Colgate-McFarlane
----
  "You can get all your daily vitamins from 52 pints of guiness, and a
glass of milk"




  reply	other threads:[~2009-12-18 13:27 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 [this message]
2009-12-28 11:05 ` Andy Wingo

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=2e6d10880912180527k3ae5af5aqa2eb0f9bc5719cb5@mail.gmail.com \
    --to=tcolgate@gmail.com \
    --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).