From: Stefan Monnier <monnier@iro.umontreal.ca>
To: help-gnu-emacs@gnu.org
Subject: Re: Defining functions on the fly
Date: Tue, 16 Jun 2015 21:12:27 -0400 [thread overview]
Message-ID: <jwvk2v3f8dc.fsf-monnier+gnu.emacs.help@gnu.org> (raw)
In-Reply-To: 1a9b8f2a-8014-419a-91b1-e2413fe92e13@googlegroups.com
>> > (fset (function name-of-function)
>> [...]
>> > (define name-of-function
>> Actually, `fset' is more like Scheme's `set!',
> How so?
Exactly in the sense you describe:
> `define' is typically used if or when a symbol has yet to be bound to
> either a lambda function or value.
> set! is used to destructively re-bind something to a symbol already
> bound to something.
`defun' macroexpands to `defalias' rather than to `fset'.
>> so if it's the *definition* of a function, you should use `defalias'
>> which is more like Scheme's `define'.
> I don't see it that way, but if works to one's satisfaction then why not?
Actually, they don't do the same thing. E.g. fset will throw
away/override any advice you may have applied to that function, whereas
defalias will combine the new definition with the pieces of advice.
Stefan
next prev parent reply other threads:[~2015-06-17 1:12 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.5020.1434360277.904.help-gnu-emacs@gnu.org>
2015-06-15 9:57 ` Defining functions on the fly Pascal J. Bourguignon
2015-06-15 11:21 ` Andreas Röhler
2015-06-15 11:52 ` Tassilo Horn
2015-06-15 12:06 ` Andreas Röhler
2015-06-15 12:43 ` Andreas Röhler
2015-06-15 23:51 ` Gene
2015-06-16 1:14 ` Stefan Monnier
2015-06-17 0:24 ` Gene
2015-06-17 1:12 ` Stefan Monnier [this message]
2015-06-16 5:47 ` Andreas Röhler
2015-06-15 9:24 Andreas Röhler
2015-06-15 9:32 ` Dmitry Gutov
2015-06-15 9:47 ` Alexis
2015-06-15 10:20 ` Andreas Röhler
2015-06-15 10:37 ` Alexis
2015-06-15 10:41 ` Michael Heerdegen
2015-06-15 10:42 ` Tassilo Horn
2015-06-15 11:01 ` Alexis
2015-06-15 11:19 ` Michael Heerdegen
2015-06-15 11:24 ` Tassilo Horn
2015-06-15 11:31 ` Michael Heerdegen
2015-06-15 10:00 ` Tassilo Horn
2015-06-15 10:33 ` Andreas Röhler
[not found] ` <mailman.5022.1434361680.904.help-gnu-emacs@gnu.org>
2015-06-15 12:52 ` Stefan Monnier
2015-06-16 5:59 ` Andreas Röhler
2015-06-16 7:01 ` Tassilo Horn
2015-06-16 9:22 ` Andreas Röhler
2015-06-16 11:12 ` Tassilo Horn
2015-06-16 11:40 ` Andreas Röhler
2015-06-16 13:10 ` Tassilo Horn
2015-06-16 15:46 ` Andreas Röhler
[not found] ` <mailman.5109.1434469628.904.help-gnu-emacs@gnu.org>
2015-06-16 22:34 ` Stefan Monnier
[not found] ` <mailman.5090.1434454815.904.help-gnu-emacs@gnu.org>
2015-06-16 16:13 ` Pascal J. Bourguignon
2015-06-16 18:30 ` Andreas Röhler
2015-06-16 9:42 ` Andreas Röhler
[not found] ` <mailman.5084.1434446560.904.help-gnu-emacs@gnu.org>
2015-06-16 9:50 ` Pascal J. Bourguignon
2015-06-16 10:26 ` Andreas Röhler
[not found] ` <mailman.5087.1434450412.904.help-gnu-emacs@gnu.org>
2015-06-16 11:35 ` Pascal J. Bourguignon
[not found] ` <mailman.5085.1434447782.904.help-gnu-emacs@gnu.org>
2015-06-16 22:32 ` Stefan Monnier
[not found] ` <mailman.5075.1434434385.904.help-gnu-emacs@gnu.org>
2015-06-16 22:23 ` Stefan Monnier
2015-06-17 6:13 ` Andreas Röhler
[not found] ` <mailman.5137.1434522533.904.help-gnu-emacs@gnu.org>
2015-06-17 14:30 ` Stefan Monnier
2015-06-17 16:40 ` Andreas Röhler
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=jwvk2v3f8dc.fsf-monnier+gnu.emacs.help@gnu.org \
--to=monnier@iro.umontreal.ca \
--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.
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).