From: Tim X <timx@nospam.dev.null>
To: help-gnu-emacs@gnu.org
Subject: Re: Redefining functions and variables
Date: Fri, 30 Jul 2010 08:22:15 +1000 [thread overview]
Message-ID: <87y6cund2g.fsf@puma.rapttech.com.au> (raw)
In-Reply-To: 878w4u9gcq.fsf@gnu.org
Johan Bockgård <bojohan+news@gnu.org> writes:
> Elena <egarrulo@gmail.com> writes:
>
>>> (defmacro defun (name args &rest body)
>>> `(progn
>>> (message "defining %S" name)
>>> (,old-defun ,name ,args ,@body)))
>>
>> This is very close to what I was looking for.
>
> Note that neither defadvice nor redefinition of defun will work for
> (already) byte compiled code.
>
>
> (byte-compile (lambda () (defun foo ()))) =>
>
> #[nil "..." [defalias foo #[nil "..." [nil] 1]] 3]
> ^
> no `defun' after byte compilation
Not sure what you mean here, but I have lots of defadvice that is
defined for functions that are already defined and byte compiled which
work fine i.e. I use defadvice to advise standard emacs lisp functions
regularly without problems.
Tim
--
tcross (at) rapttech dot com dot au
prev parent reply other threads:[~2010-07-29 22:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-27 15:12 Redefining functions and variables Elena
2010-07-27 20:21 ` Stefan Monnier
2010-07-27 22:16 ` Elena
2010-07-28 0:35 ` Andreas Politz
2010-07-28 7:51 ` Elena
2010-07-28 14:29 ` Elena
2010-07-28 18:48 ` Andreas Politz
2010-07-28 20:37 ` Pascal J. Bourguignon
2010-07-29 8:32 ` Elena
2010-07-29 9:57 ` Stefan Monnier
2010-07-29 10:16 ` Elena
2010-07-29 13:14 ` Stefan Monnier
2010-07-30 19:32 ` Uday S Reddy
2010-07-29 10:31 ` Andreas Politz
2010-07-29 11:46 ` Johan Bockgård
2010-07-29 15:54 ` Andreas Politz
2010-07-29 12:41 ` Tim X
2010-07-29 10:03 ` Pascal J. Bourguignon
2010-07-29 10:28 ` Elena
2010-07-29 20:35 ` Johan Bockgård
2010-07-29 22:22 ` Tim X [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=87y6cund2g.fsf@puma.rapttech.com.au \
--to=timx@nospam.dev.null \
--cc=help-gnu-emacs@gnu.org \
/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.