[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Brittleness of called-interactively-p
From: |
Richard Stallman |
Subject: |
Re: Brittleness of called-interactively-p |
Date: |
Mon, 13 Jul 2015 19:03:37 -0400 |
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> If I understand right, an instrumenting code must be aware of the variable
> name used internally by a function. That is, when writing defadvice I should
> look inside foo in order to figure out that internally it's using in-foo,
Yes. However, there needs to be a way to find that out
in order for calls to the function to bind that variable.
If we provide a convenient function to get that variable name, perhaps
called called-interactively-binding-variable, it will be easy
for advising and other instrumenters to do what is needed.
Advising has to do SOMETHING about this, because if the advice makes a
wrapper, and it is necessary for that wrapper to bind the variable (or
whatever is used) _instead_ of the original function.
--
Dr Richard Stallman
President, Free Software Foundation (gnu.org, fsf.org)
Internet Hall-of-Famer (internethalloffame.org)
Skype: No way! See stallman.org/skype.html.
Re: Brittleness of called-interactively-p, raman, 2015/07/18
Re: Brittleness of called-interactively-p, Richard Stallman, 2015/07/12
Re: Brittleness of called-interactively-p, Przemysław Wojnowski, 2015/07/17