unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lynn Winebarger <owinebar@gmail.com>
To: Damien Cassou <damien@cassou.me>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel <emacs-devel@gnu.org>
Subject: Re: Using the content of a dynamic variable in a macro
Date: Sat, 25 Feb 2023 07:32:00 -0500	[thread overview]
Message-ID: <CAM=F=bCkCB32fcj5ea8EXV8w9C2C8jOitt5MvdkDwPZbi+ddWA@mail.gmail.com> (raw)
In-Reply-To: <87lekm9j2v.fsf@cassou.me>

[-- Attachment #1: Type: text/plain, Size: 809 bytes --]

On Sat, Feb 25, 2023, 5:19 AM Damien Cassou <damien@cassou.me> wrote:

> Eli Zaretskii <eliz@gnu.org> writes:
> >> Why isn't the compiler aware of the foo-var variable?
> >
> > Because lexical-binding is turned on?
>
> yes it is but I miss the deep understanding to fully understand.
>

Lexical binding isn't the issue - the variable is global in scope.
The issue is that when you explicitly run the byte-compiler in batch mode,
the "defvar" expression is only compiled, not evaluated, while the defmacro
is evaluated, and the application of the macro function is evaluated during
compilation.
Hence you need "eval-when-compile" per Tomas's response.
The reason it works in interactive mode is that the defvar is evaluated,
not compiled, and the macro function is evaluated in the run-time
environment.

Lynn

[-- Attachment #2: Type: text/html, Size: 1389 bytes --]

  reply	other threads:[~2023-02-25 12:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-25  8:34 Using the content of a dynamic variable in a macro Damien Cassou
2023-02-25  9:38 ` Eli Zaretskii
2023-02-25  9:43   ` Damien Cassou
2023-02-25 12:32     ` Lynn Winebarger [this message]
2023-02-27  3:24       ` Richard Stallman
2023-02-27 19:05         ` Basil Contovounesios
2023-02-28  2:44           ` Lynn Winebarger
2023-02-25  9:40 ` tomas
2023-02-27 19:03 ` Basil Contovounesios

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/emacs/

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

  git send-email \
    --in-reply-to='CAM=F=bCkCB32fcj5ea8EXV8w9C2C8jOitt5MvdkDwPZbi+ddWA@mail.gmail.com' \
    --to=owinebar@gmail.com \
    --cc=damien@cassou.me \
    --cc=eliz@gnu.org \
    --cc=emacs-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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).