From: Richard Stallman <rms@gnu.org>
To: "Stephen J. Turnbull" <stephen@xemacs.org>
Cc: klaus.berndl@sdm.de, nickrob@snap.net.nz, joakim@verona.se,
emacs-devel@gnu.org, raman@users.sourceforge.net, miles@gnu.org
Subject: Re: Things I would like to be added after the release
Date: Mon, 18 Jun 2007 17:31:31 -0400 [thread overview]
Message-ID: <E1I0Oot-0008DD-BF@fencepost.gnu.org> (raw)
In-Reply-To: <87hcp6aqr0.fsf@uwakimon.sk.tsukuba.ac.jp> (stephen@xemacs.org)
Of course I'm telling only a partial story here, emphasizing the
advantages of advice over hooks.
The big advantage of a hook, compared with advice, is that there is
something in the caller which informs you that a hook is run there.
It is true that anonymous lambdas as hooks are a pain,
but there's an easy solution to that: give those functions names.
next prev parent reply other threads:[~2007-06-18 21:31 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-28 9:04 Things I would like to be added after the release joakim
2007-05-29 0:02 ` Richard Stallman
2007-05-29 8:02 ` joakim
2007-05-29 9:36 ` klaus.berndl
2007-05-29 9:52 ` Michael Albinus
2007-05-29 9:56 ` David Kastrup
2007-06-16 5:01 ` T. V. Raman
2007-06-16 18:50 ` Richard Stallman
2007-06-16 23:37 ` T. V. Raman
2007-06-16 23:50 ` Miles Bader
2007-06-17 18:08 ` T. V. Raman
2007-06-17 20:15 ` Nick Roberts
2007-06-18 3:25 ` Stephen J. Turnbull
2007-06-18 21:31 ` Richard Stallman [this message]
2007-06-21 7:29 ` T. V. Raman
2007-06-21 8:09 ` Stefan Monnier
2007-06-17 8:54 ` Richard Stallman
2007-06-17 12:47 ` Stefan Monnier
2007-06-17 16:00 ` joakim
2007-05-29 10:02 ` joakim
2007-05-29 10:16 ` David Kastrup
2007-06-02 2:54 ` Richard Stallman
2007-06-04 0:17 ` Richard Stallman
2007-06-04 0:17 ` Richard Stallman
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=E1I0Oot-0008DD-BF@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=joakim@verona.se \
--cc=klaus.berndl@sdm.de \
--cc=miles@gnu.org \
--cc=nickrob@snap.net.nz \
--cc=raman@users.sourceforge.net \
--cc=stephen@xemacs.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).