public inbox for kawa@sourceware.org
 help / color / mirror / Atom feed
From: Ito Kazumitsu <kaz@maczuka.gcd.org>
To: kawa@sourceware.org
Subject: Re: Macro-generated define ignored?
Date: Thu, 10 Oct 2013 23:41:00 -0000	[thread overview]
Message-ID: <20131011.084059.437132900.kaz@maczuka.gcd.org> (raw)
In-Reply-To: <525710E0.9080202@bothner.com>

From: Per Bothner <per@bothner.com>
Subject: Re: Macro-generated define ignored?
Date: Thu, 10 Oct 2013 13:41:04 -0700

> This is an example of the power and the mystery of "macro hygiene".
> In this case there is an 'a' that is local to the syntax-rules,
> and there is an 'a' at the top-level scope.  These are distinct
> scopes,
> so the reference to 'a' at top-level does not "see" the definition
> of 'a' generated by the macro.

Thank you for your explanation.

Is it accidental that the test script with the command line option
"--script" works as "expected"?

  reply	other threads:[~2013-10-10 23:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-10 15:04 Ito Kazumitsu
2013-10-10 20:41 ` Per Bothner
2013-10-10 23:41   ` Ito Kazumitsu [this message]
2013-10-11  0:26     ` Per Bothner

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20131011.084059.437132900.kaz@maczuka.gcd.org \
    --to=kaz@maczuka.gcd.org \
    --cc=kawa@sourceware.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).