unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Basil Contovounesios <contovob@tcd.ie>
To: Richard Stallman <rms@gnu.org>
Cc: Lynn Winebarger <owinebar@gmail.com>,
	 damien@cassou.me,  eliz@gnu.org, emacs-devel@gnu.org
Subject: Re: Using the content of a dynamic variable in a macro
Date: Mon, 27 Feb 2023 19:05:42 +0000	[thread overview]
Message-ID: <87h6v753p5.fsf@tcd.ie> (raw)
In-Reply-To: <E1pWU7q-0002bW-JN@fencepost.gnu.org> (Richard Stallman's message of "Sun, 26 Feb 2023 22:24:30 -0500")

Richard Stallman [2023-02-26 22:24 -0500] wrote:

>   > 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.
>
> Should we change this to evaluate defvar in batch mode?

The byte-compiler avoids evaluating the defvar also in non-batch mode.

So the question is how much of the code that it is compiling should the
byte-compiler evaluate.

We may need to reuse or possibly extend the notions of Lisp code safety
we have before the byte-compiler can start evaluating arbitrary
expressions.  I'm not sure it's worth the complexity.

-- 
Basil



  reply	other threads:[~2023-02-27 19:05 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
2023-02-27  3:24       ` Richard Stallman
2023-02-27 19:05         ` Basil Contovounesios [this message]
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=87h6v753p5.fsf@tcd.ie \
    --to=contovob@tcd.ie \
    --cc=damien@cassou.me \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=owinebar@gmail.com \
    --cc=rms@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).