From: Barry Fishman <barry_fishman@acm.org>
Subject: Re: new Mail-Followup-To patch...please take a look...
Date: Fri, 26 Oct 2001 21:19:14 -0400 [thread overview]
Message-ID: <m366917uct.fsf@barry_fishman.att.net> (raw)
In-Reply-To: <vafofmu5301.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de>
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> "Davide G. M. Salvetti" <salve@debian.org> writes:
>
>> Ok for '(lambda). But what's the point in writing #'(lambda ...) if
>> (lambda ...) already evaluates to it (being lambda a macro)? Is that
>> some kind of stylistic convention, or there is really something more?
>
> I think that (lambda ...) doesn't work in CL; you have to use
> #'(lambda ...) there. It seems that some Emacs Lisp programmers
> prefer to use CL-like notation. Maybe they want to support the CLErik
> Conspiracy.
According to the CL hyperspec:
(lambda lambda-list [[declaration* | documentation]] form*)
== (function (lambda lambda-list [[declaration* | documentation]] form*))
== #'(lambda lambda-list [[declaration* | documentation]] form*)
And the #' didn't seem to be needed in any of the CL systems I tried.
However, Guy Steele's "Common Lisp, The Language Second Edition",
Section 5.2 states quite explicitly the opposite. I guess its more
recent than 1990, probably introduced by scheme people who infiltrated
an ANSI draft review by posing as MIT janitors.
Barry Fishman
next prev parent reply other threads:[~2001-10-27 1:19 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-23 15:24 Josh Huber
2001-10-23 15:42 ` Josh Huber
2001-10-23 16:32 ` Paul Jarc
2001-10-23 16:54 ` Josh Huber
2001-10-23 17:45 ` Paul Jarc
2001-10-23 18:54 ` Matt Armstrong
2001-10-23 19:53 ` Paul Jarc
2001-10-24 0:34 ` Josh Huber
2001-10-24 11:35 ` Per Abrahamsen
2001-10-24 12:48 ` Josh Huber
2001-10-24 16:31 ` Paul Jarc
2001-10-24 17:08 ` Per Abrahamsen
2001-10-24 17:18 ` Paul Jarc
2001-10-26 6:24 ` Kai Großjohann
2001-10-27 23:23 ` Florian Weimer
2001-10-23 16:56 ` Josh Huber
2001-10-23 17:32 ` Per Abrahamsen
2001-10-23 23:53 ` Josh Huber
2001-10-23 22:40 ` Davide G. M. Salvetti
2001-10-24 1:40 ` Paul Jarc
2001-10-24 12:45 ` Davide G. M. Salvetti
2001-10-24 13:44 ` Samuel Padgett
2001-10-24 15:23 ` Paul Jarc
2001-10-24 15:42 ` Per Abrahamsen
2001-10-24 15:51 ` Samuel Padgett
2001-10-26 6:28 ` Kai Großjohann
2001-10-27 1:19 ` Barry Fishman [this message]
2001-10-29 14:49 ` Kai Großjohann
2001-10-27 22:27 ` Florian Weimer
2001-10-24 1:59 ` Josh Huber
2001-10-24 15:02 ` Per Abrahamsen
2001-10-24 16:48 ` Paul Jarc
2001-10-24 17:13 ` Per Abrahamsen
2001-10-25 1:52 ` Josh Huber
2001-10-24 16:13 ` Paul Jarc
2001-10-24 17:19 ` Per Abrahamsen
2001-10-24 17:28 ` Paul Jarc
2001-10-24 17:38 ` Per Abrahamsen
2001-10-25 1:45 ` Josh Huber
2001-10-25 18:48 ` Josh Huber
2001-10-29 21:58 ` Matt Armstrong
2001-10-29 22:19 ` Josh Huber
2001-10-29 22:31 ` Paul Jarc
2001-10-30 2:47 ` Josh Huber
2001-10-30 3:11 ` Paul Jarc
2001-10-30 3:49 ` Matt Armstrong
2001-10-30 12:55 ` Per Abrahamsen
2001-10-30 15:31 ` Josh Huber
2001-10-31 13:44 ` ShengHuo ZHU
2001-10-31 17:28 ` Matt Armstrong
2001-10-31 17:51 ` Josh Huber
2001-10-31 18:22 ` ShengHuo ZHU
2001-10-26 6:34 ` Kai Großjohann
2001-10-26 9:07 ` Per Abrahamsen
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=m366917uct.fsf@barry_fishman.att.net \
--to=barry_fishman@acm.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 NNTP newsgroup(s).