From: Michael Heerdegen <michael_heerdegen@web.de>
To: Alan Mackenzie <acm@muc.de>
Cc: 65620@debbugs.gnu.org
Subject: bug#65620: void function edebug-after
Date: Thu, 31 Aug 2023 01:09:11 +0200 [thread overview]
Message-ID: <87ledsku08.fsf@web.de> (raw)
In-Reply-To: <ZO88uT-KzimjHKaC@ACM> (Alan Mackenzie's message of "Wed, 30 Aug 2023 12:57:29 +0000")
Alan Mackenzie <acm@muc.de> writes:
> (defmacro hash-if (condition then-form &rest else-forms)
> "A conditional compilation macro analogous to C's #if.
> Evaluate CONDITION at macro-expansion time. If it is non-nil,
> expand the macro to THEN-FORM. Otherwise expand it to ELSE-FORMS
> enclosed in a `progn' form. ELSE-FORMS may be empty."
> (declare (indent 2)
> (debug (form sexp &rest sexp)))
> (if (eval condition lexical-binding)
> then-form
> (cons 'progn else-forms)))
Dunno if someone is able to fix this (I'm not). Until then using
`def-form` `or `sexp` instead of `form` works in a better way (the
former edebugs CONDITION when instrumenting, the latter would omit
edebugging the CONDITION entirely).
Anyway, the key point in the above example is that macroexpanding (while
instrumenting) combined with the `eval' call seems to lead to the
evaluation of instrumented code outside of an Edebug session when
CONDITION is instrumented using `form`. `eval-when-compile' uses
`def-form` for example - I guess using `form` in this case doesn't work
as one might expect.
Michael.
next prev parent reply other threads:[~2023-08-30 23:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-30 12:57 bug#65620: void function edebug-after Alan Mackenzie
2023-08-30 23:09 ` Michael Heerdegen [this message]
2023-08-31 7:55 ` Gerd Möllmann
2023-08-31 8:02 ` Gerd Möllmann
2023-08-31 13:50 ` Alan Mackenzie
2023-08-31 14:41 ` Gerd Möllmann
2023-09-01 9:23 ` Alan Mackenzie
2023-09-01 12:27 ` Gerd Möllmann
2023-09-01 21:27 ` Alan Mackenzie
2023-09-02 4:27 ` Gerd Möllmann
2023-09-02 13:10 ` Alan Mackenzie
2023-09-02 13:15 ` Gerd Möllmann
2023-09-02 13:57 ` Alan Mackenzie
2023-09-03 4:29 ` Michael Heerdegen
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=87ledsku08.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=65620@debbugs.gnu.org \
--cc=acm@muc.de \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.