[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#60450: 30.0.50; Strange behavior of compiler macros in *scratch*
From: |
Lynn Winebarger |
Subject: |
bug#60450: 30.0.50; Strange behavior of compiler macros in *scratch* |
Date: |
Sun, 7 May 2023 21:59:51 -0400 |
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
- bug#60450: 30.0.50; Strange behavior of compiler macros in *scratch*,
Lynn Winebarger <=