From: "Drew Adams" <drew.adams@oracle.com>
To: "'Stefan Monnier'" <monnier@iro.umontreal.ca>,
"'Lennart Borgman'" <lennart.borgman@gmail.com>
Cc: 'Andreas Schwab' <schwab@linux-m68k.org>, 5863@debbugs.gnu.org
Subject: bug#5863: defadvice in byte compiled file does not work
Date: Thu, 8 Apr 2010 20:37:55 -0700 [thread overview]
Message-ID: <3334DEC2827B4F83B29BC6ED08D3CF39@us.oracle.com> (raw)
In-Reply-To: <jwvzl1d8jsk.fsf-monnier+emacs@gnu.org>
> > The info page I pointed to says that defadvice should work for
> > primitives called from lisp code. And that is what does
> > not work for me here.
>
> For such uses, there are several categories of functions:
> - functions that have their own byte-code (things like widen,
> car, cdr, ...).
> - functions that are implemented in C but don't have their own
> byte-code.
> - other functions.
>
> Pieces of advice on the first kind of functions only work for
> calls from interpreted Lisp code.
> Pieces of advice on the second kind of functions only work for
> calls from Lisp code (both interpreted and byte-compiled).
Please document the behavior in the manual, not just here. Thx.
next prev parent reply other threads:[~2010-04-09 3:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-08 15:26 bug#5863: defadvice in byte compiled file does not work Lennart Borgman
2010-04-08 15:50 ` Andreas Schwab
2010-04-08 15:57 ` Lennart Borgman
2010-04-08 16:06 ` Andreas Schwab
2010-04-08 16:22 ` Lennart Borgman
2010-04-08 16:55 ` Andreas Schwab
2010-04-08 16:56 ` Lennart Borgman
2010-04-08 17:04 ` Andreas Schwab
2010-04-08 17:06 ` Lennart Borgman
2010-04-08 18:22 ` Lennart Borgman
2010-04-08 21:52 ` Andreas Schwab
2010-04-08 23:13 ` Lennart Borgman
2010-04-09 0:19 ` Lennart Borgman
2010-04-09 2:06 ` Stefan Monnier
2010-04-09 3:37 ` Drew Adams [this message]
2020-11-19 3:23 ` Stefan Kangas
2020-11-19 5:20 ` Stefan Monnier
2020-11-19 8:14 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-11-20 5:07 ` Stefan Kangas
2020-11-27 11:45 ` Stefan Kangas
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=3334DEC2827B4F83B29BC6ED08D3CF39@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=5863@debbugs.gnu.org \
--cc=lennart.borgman@gmail.com \
--cc=monnier@iro.umontreal.ca \
--cc=schwab@linux-m68k.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).