unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lynn Winebarger <owinebar@gmail.com>
To: 60450@debbugs.gnu.org
Subject: bug#60450: 30.0.50; Strange behavior of compiler macros in *scratch*
Date: Sun, 7 May 2023 21:59:51 -0400	[thread overview]
Message-ID: <CAM=F=bC36h5vRMnG=NAQOpsuGnitNCMznBvMM6=NBM1hMRidfQ@mail.gmail.com> (raw)
In-Reply-To: <d14aa519-69ce-b71e-4c07-6c654a28ab03@gmail.com>

I was going to open a feature request bug for a function to
specifically expand compiler-macros, but if the behavior reported here
is intended, then I don't really need to.

However, if this is the intended behavior of macroexpand-all, it is
inconsistent with the documentation, which says:

     ‘macroexpand-all’ expands macros like ‘macroexpand’, but will look
     for and expand all macros in FORM, not just at the top-level.  If
     no macros are expanded, the return value is ‘eq’ to FORM.

But macroexpand is defined in C source code, and definitely *only*
expands function symbols whose value has a car of 'macro.

Could someone determine if this is a bug in macroexpand-all (e.g. it
should be checking whether it is being called while byte-compiling),
or just a documentation bug?

Thanks,
Lynn





  parent reply	other threads:[~2023-05-08  1:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-31 13:22 bug#60450: 30.0.50; Strange behavior of compiler macros in *scratch* Gerd Möllmann
2022-12-31 14:42 ` Andreas Schwab
2023-01-01  6:34   ` Gerd Möllmann
2023-05-08  1:59 ` Lynn Winebarger [this message]
2023-05-08 11:29   ` Eli Zaretskii
2023-05-08 12:25 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-05-18  6:33   ` Gerd Möllmann

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=bC36h5vRMnG=NAQOpsuGnitNCMznBvMM6=NBM1hMRidfQ@mail.gmail.com' \
    --to=owinebar@gmail.com \
    --cc=60450@debbugs.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).