unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Andy Wingo <wingo@pobox.com>
Cc: 13995@debbugs.gnu.org
Subject: bug#13995: Problem with macros whose expansions define and use auxiliary macros
Date: Wed, 20 Mar 2013 13:30:05 -0400	[thread overview]
Message-ID: <87d2uuc736.fsf@tines.lan> (raw)
In-Reply-To: <87boae1c9w.fsf@pobox.com> (Andy Wingo's message of "Wed, 20 Mar 2013 13:33:31 +0100")

Andy Wingo <wingo@pobox.com> writes:
> Have you tried master?

I just did, and my toy example works there.  Do you think that commit
de41e56492666801078e73860a358e1c63cbc8c2 is the reason?

It would be nice to get this working in stable-2.0 as well, but I guess
that would require working through our disagreement over the handling of
macro-introduced top-level identifiers.

  http://lists.gnu.org/archive/html/guile-devel/2011-11/msg00016.html

I still strongly believe that we should follow the standard behavior,
namely that each invocation of a macro must introduce fresh identifiers
(even if the macro operands are identical) just as every invocation of a
procedure must introduce fresh lexical variables (even if the procedure
arguments are identical).

    Regards,
      Mark





  reply	other threads:[~2013-03-20 17:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-18 23:11 bug#13995: Problem with macros whose expansions define and use auxiliary macros Mark H Weaver
2013-03-20 12:33 ` Andy Wingo
2013-03-20 17:30   ` Mark H Weaver [this message]
2016-06-20 20:22 ` 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=87d2uuc736.fsf@tines.lan \
    --to=mhw@netris.org \
    --cc=13995@debbugs.gnu.org \
    --cc=wingo@pobox.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).