unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Marcin Borkowski <mbork@mbork.pl>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Dynamically constructing advice behaves strangely
Date: Sun, 14 Feb 2016 21:58:46 +0100	[thread overview]
Message-ID: <87egcf2em1.fsf@mbork.pl> (raw)
In-Reply-To: <87ziv39u0s.fsf@web.de>


On 2016-02-14, at 16:44, Michael Heerdegen <michael_heerdegen@web.de> wrote:

> Marcin Borkowski <mbork@mbork.pl> writes:
>
>> (defun add-constructed-advice (fun)
>>   "Add a constructed advice to function foo."
>>   (let* ((fun-name (symbol-name fun))
>> 	 (length-sym
>> 	  (make-symbol (concat "length-of-" fun-name)))
>> 	 (piece-of-advice-sym
>> 	  (make-symbol (concat "advice-for-" fun-name)))
>> 	 (piece-of-advice (lambda (orig-fun &rest args)
>> 			    (apply orig-fun args)
>> 			    (message "This function's name had length %s."
>> 				     (symbol-value length-sym)))))
>
> Also, `length-sym' doesn't have to be an uninterned symbol here.  You
> use lexical-binding anyway (by referring to the value of the (interned!)
> symbol named "length-sym".  You don't even have to use a symbol with a
> unique name.  Just use a simple (lexical) variable for the length,
> e.g. `advice-length', and
>
> (message "This function's name had length %s." advice-length)
>
> etc. (your piece of advice is a closure!).

I know, and in fact I'm making use of lexical binding in my "real"
code.  This was just a trimmed-down version for the sake of asking here.

> Michael.

Best,

-- 
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Faculty of Mathematics and Computer Science
Adam Mickiewicz University



      reply	other threads:[~2016-02-14 20:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-14 14:59 Dynamically constructing advice behaves strangely Marcin Borkowski
2016-02-14 15:34 ` Michael Heerdegen
2016-02-14 20:57   ` Marcin Borkowski
2016-02-14 15:44 ` Michael Heerdegen
2016-02-14 20:58   ` Marcin Borkowski [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

  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=87egcf2em1.fsf@mbork.pl \
    --to=mbork@mbork.pl \
    --cc=help-gnu-emacs@gnu.org \
    --cc=michael_heerdegen@web.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.
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).