From: Michael Heerdegen <michael_heerdegen@web.de>
To: Alan Mackenzie <acm@muc.de>
Cc: "Gerd Möllmann" <gerd.moellmann@gmail.com>, 65620@debbugs.gnu.org
Subject: bug#65620: void function edebug-after
Date: Sun, 03 Sep 2023 06:29:29 +0200 [thread overview]
Message-ID: <87v8cr3mmu.fsf@web.de> (raw)
In-Reply-To: <ZPJXMHC2WRZ-oDyS@ACM> (Alan Mackenzie's message of "Fri, 1 Sep 2023 21:27:12 +0000")
Hello Alan,
> -(defalias 'edebug-before nil
> +;; The following versions of `edebug-before' and `edebug-after' exist
> +;; to handle the error which occurs if either of them gets called
> +;; without an enclosing `edebug-enter'. This can happen, for example,
> +;; when a macro mistakenly has a `form' element in its edebug spec,
> +;; and it additionally, at macro-expansion time, calls `eval',
> +;; `apply', or `funcall' (etc.)
I wonder whether what you say about `apply', or `funcall' is true: What
you can "call" in the macro expander is either a symbol or a function
_form_, i.e., a quoted lambda. Maybe this quoted lambda is instrumented
by Edebug when forcing it in the debug spec, dunno, but specifying a
lambda expression in a macro call that is then called by the macro at
expansion time as quoted lambda makes no sense, one would rather make
the macro accept a form, or eval the function form in the expansion at
run-time.
So I'm not sure whether `apply' and `funcall' are really like `eval' in
this case.
Or - if the argument to funcall is a symbol - my question is what would
happen when macro expansion calls instrumented functions the normal way
(F . ARGS). This works correctly, right?
Michael.
prev parent reply other threads:[~2023-09-03 4:29 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
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 [this message]
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=87v8cr3mmu.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=65620@debbugs.gnu.org \
--cc=acm@muc.de \
--cc=gerd.moellmann@gmail.com \
/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.