From: Sebastian Tennant <sebyte@smolny.plus.com>
To: help-gnu-emacs@gnu.org
Subject: Re: add-hook
Date: Thu, 07 Jun 2007 13:00:44 +0300 [thread overview]
Message-ID: <87r6ooccdv.fsf@moley.org> (raw)
In-Reply-To: 87tztktes8.fsf@ambire.localdomain
Quoth Thien-Thi Nguyen <ttn@gnuvola.org>:
> () Sebastian Tennant <sebyte@smolny.plus.com>
> () Thu, 07 Jun 2007 03:20:33 +0300
>
> Perhaps someone could explain why it is lambda
> functions don't need to be quoted in this context?
>
> in elisp, the form `(lambda ARGS BODY)' is self-quoting in
> all contexts, like numbers and strings. sometimes you see:
>
> (function (lambda ...))
> #'(lambda ...)
>
> these serve as hints to the byte compiler that the form
> should be compiled. on the other hand, if you see:
>
> '(lambda ...)
>
> then that tells the compiler to treat the form as data (DON'T compile).
> if you aren't byte compiling, quoting is strictly optional.
>
> thi
Many thanks.
I was aware that everything boils down to lambda functions in lisp but
it hadn't occured to me that they are self quoting in all contexts,
although now I think about it I realise they _have_ to be
self-quoting, given that they are one of the fundamental building
blocks...
(info "(elisp)Anonymous Functions"):
In Lisp, a function is a list that starts with `lambda', a byte-code
function compiled from such a list, or alternatively a primitive
subr-object; names are "extra."
Sebastian
next prev parent reply other threads:[~2007-06-07 10:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-06 11:26 add-hook Sebastian Tennant
2007-06-07 0:20 ` add-hook Sebastian Tennant
[not found] ` <mailman.1696.1181175524.32220.help-gnu-emacs@gnu.org>
2007-06-07 7:16 ` add-hook Thien-Thi Nguyen
2007-06-07 10:00 ` Sebastian Tennant [this message]
[not found] ` <mailman.1711.1181210337.32220.help-gnu-emacs@gnu.org>
2007-06-07 14:01 ` add-hook Thien-Thi Nguyen
[not found] <mailman.1634.1181129906.32220.help-gnu-emacs@gnu.org>
2007-06-06 12:04 ` add-hook Katsumi Yamaoka
2007-06-06 20:41 ` add-hook Robert D. Crawford
-- strict thread matches above, loose matches on Subject: below --
2011-06-04 13:00 add-hook daniele.g
2011-06-04 14:11 ` add-hook Teemu Likonen
2011-06-04 18:35 ` add-hook daniele.g
2011-06-05 10:58 ` add-hook Richard Riley
2011-06-05 18:58 ` add-hook daniele.g
2011-06-05 20:26 ` add-hook Richard Riley
2011-06-05 22:28 ` add-hook daniele.g
2011-06-05 23:33 ` add-hook Richard Riley
2013-01-25 19:03 add-hook Perry Smith
2013-01-25 19:18 ` add-hook Drew Adams
2013-01-26 4:03 ` add-hook Dmitry Gutov
[not found] ` <mailman.18346.1359173059.855.help-gnu-emacs@gnu.org>
2013-01-26 5:33 ` add-hook Barry Margolin
2013-01-26 6:21 ` add-hook Dmitry Gutov
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=87r6ooccdv.fsf@moley.org \
--to=sebyte@smolny.plus.com \
--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).