From: Drew Adams <drew.adams@oracle.com>
To: "Pascal J. Bourguignon" <pjb@informatimago.com>, help-gnu-emacs@gnu.org
Subject: RE: member returns list
Date: Sun, 6 Sep 2015 19:37:55 -0700 (PDT) [thread overview]
Message-ID: <91d13d72-cc94-4a52-ab0a-15db05f82c73@default> (raw)
In-Reply-To: <87k2s3b5xw.fsf@kuiper.lan.informatimago.com>
> But basically, he started GNU emacs and designing emacs lisp slightly
> beforem the CL standardization process started, and it was far from
> obviouos that it would succeed (it took ten years!).
Hm... Dunno when you want to say that RMS "started" designing
Emacs Lisp. But I think I disagree with what I think you are
saying about when "the CL standardization process started".
The first public release of GNU Emacs was in 1985. Common
Lisp was designed over a period of years prior to that, and RMS
was at least somewhat involved with that design process (he was
well aware of it, to say the least).
Common Lisp was defined by 1984. The book that specified its
definition, Common Lisp the Language, was published in 1984
(I'm looking at my 1984 copy now), and it is quite clear from
that book that the language design that it presents (specifies,
in detail) was agreed upon by all of the design participants.
It is a thoroughgoing specification of the language, and as
such it was used as the guide when implementing CL here and
there.
Was that a "standard". I would say so. It was a full
definition, and it thus allowed people to go out and develop
implementations. Whether it was a "standard" blessed by this
or that standards body is a moot point, IMO.
And there were already working implementations of Common Lisp
in 1984. It was being used by programmers in various labs in
1984. And new Common Lisp implementations were fast underway
in 1984 (e.g. for new Lisp machines).
I was using Kyoto Common Lisp in 1984, for instance. It was not
a great implementation at that point, but it was usable. It was
developed just on the basis of studying the spec (CLtL).
https://en.wikipedia.org/wiki/Kyoto_Common_Lisp
Not only was Common Lisp defined by 1984, it was even already
criticized in a paper in the 1984 Symposium on Lisp and
Functional Programming, "Critique of Common Lisp".
See The Evolution of Lisp, http://www.dreamsongs.com/Files/Hopl2.pdf
From another recent thread here ("print out all members of a list"):
>>>> How is that possible, since Emacs Lisp came out AFTER Scheme and Common
>>>> Lisp? CLtL was published in 1984, the same year Stallman started
>>>> writing GNU Emacs? And Scheme is older, since CL took a number of ideas
>>>> from it (most notably lexical scoping).
>>>
>>> At the same time as CL.
>>> The CL standard was completed in 1994. 1984 only marks the beginning
>>> of the standardization effort.
I disagree with that characterization. The fact that Common Lisp
continued to be refined as a standard, and the fact that CLOS and
ANSI Common Lisp came later, does not mean that CL had not already
been defined by 1984.
> For example, Franz, Inc. switched over to CL only after 1985
> and had CL available only in 1986.
Franz Lisp was widely distributed and mature, while CL had few
implementations at that point. Eventually Franz Inc. was formed
and it produced its own implementation of Common Lisp.
But the fact that Franz Inc. did not have a CL in 1984 does not
mean that CL had not been designed by then, let alone that it
was not defined until 1994! Other CL implementations existed
in 1984, and still others were in the process of development.
This development was all happening (rapidly) because CL had
already been designed, as a standard. The mere fact that
Franz Inc. could and would set out to implement its own CL
after 1984 underlines the fact that CL had already been
defined by then.
> http://franz.com/about/company.history.lhtml
> http://emacswiki.org/emacs/EmacsHistory
next prev parent reply other threads:[~2015-09-07 2:37 UTC|newest]
Thread overview: 103+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-01 15:50 To `boundp' or not to `boundp'? Alexander Shukaev
2015-09-01 15:51 ` Dmitry Gutov
2015-09-01 15:53 ` Alexander Shukaev
2015-09-01 16:42 ` Drew Adams
2015-09-01 17:13 ` Michael Heerdegen
2015-09-01 18:00 ` Drew Adams
[not found] ` <mailman.331.1441125765.19560.help-gnu-emacs@gnu.org>
2015-09-01 20:20 ` Barry Margolin
2015-09-01 23:37 ` member returns list (was: Re: To `boundp' or not to `boundp'?) Emanuel Berg
2015-09-02 0:10 ` Drew Adams
2015-09-02 0:27 ` Emanuel Berg
2015-09-02 0:38 ` Drew Adams
2015-09-02 1:17 ` Emanuel Berg
2015-09-02 6:21 ` Drew Adams
2015-09-02 21:20 ` Emanuel Berg
[not found] ` <mailman.370.1441156160.19560.help-gnu-emacs@gnu.org>
2015-09-03 5:17 ` member returns list Pascal J. Bourguignon
2015-09-04 0:26 ` Emanuel Berg
2015-09-02 16:45 ` Michael Heerdegen
2015-09-02 21:47 ` Emanuel Berg
2015-09-02 22:09 ` Michael Heerdegen
2015-09-02 22:11 ` Drew Adams
2015-09-02 22:13 ` Marcin Borkowski
2015-09-04 1:03 ` Emanuel Berg
2015-09-04 6:50 ` Marcin Borkowski
2015-09-05 17:35 ` Emanuel Berg
2015-09-05 17:55 ` Random832
2015-09-05 18:09 ` Emanuel Berg
2015-09-05 21:04 ` Random832
2015-09-06 2:57 ` Emanuel Berg
[not found] ` <mailman.552.1441475739.19560.help-gnu-emacs@gnu.org>
2015-09-05 23:39 ` Pascal J. Bourguignon
2015-09-06 2:46 ` Emanuel Berg
2015-09-09 1:48 ` Robert Thorpe
2015-09-09 2:44 ` Pascal J. Bourguignon
2015-09-09 3:19 ` John Mastro
2015-09-10 0:25 ` Emanuel Berg
[not found] ` <mailman.557.1441507097.19560.help-gnu-emacs@gnu.org>
2015-09-06 21:20 ` Pascal J. Bourguignon
2015-09-06 23:33 ` Emanuel Berg
[not found] ` <mailman.598.1441581917.19560.help-gnu-emacs@gnu.org>
2015-09-06 23:47 ` Pascal J. Bourguignon
2015-09-07 1:29 ` Pascal J. Bourguignon
2015-09-07 2:25 ` Emanuel Berg
2015-09-09 1:44 ` Robert Thorpe
2015-09-10 0:23 ` Emanuel Berg
[not found] ` <mailman.793.1441844665.19560.help-gnu-emacs@gnu.org>
2015-09-10 2:01 ` Pascal J. Bourguignon
2015-09-10 2:32 ` Emanuel Berg
[not found] ` <ECCA0E56-A051-4D38-8CBB-6CE9208BB047@openmailbox.org>
2015-09-11 1:32 ` Emanuel Berg
2015-09-11 1:46 ` Emanuel Berg
[not found] ` <mailman.797.1441852386.19560.help-gnu-emacs@gnu.org>
2015-09-10 4:21 ` Pascal J. Bourguignon
2015-09-10 18:09 ` Alex Kost
2015-09-11 1:01 ` Random832
2015-09-11 1:28 ` Emanuel Berg
2015-09-11 2:01 ` Emanuel Berg
2015-09-11 2:52 ` Random832
[not found] ` <mailman.890.1441936900.19560.help-gnu-emacs@gnu.org>
2015-09-11 2:27 ` Pascal J. Bourguignon
2015-09-12 0:10 ` Emanuel Berg
2015-09-11 2:37 ` Ian Zimmerman
2015-09-11 1:03 ` Emanuel Berg
2015-09-11 0:57 ` Emanuel Berg
2015-09-11 5:42 ` tomas
2015-09-12 0:18 ` Emanuel Berg
2015-09-13 8:12 ` tomas
[not found] ` <mailman.897.1441950163.19560.help-gnu-emacs@gnu.org>
2015-09-11 23:29 ` Pascal J. Bourguignon
2015-09-12 0:20 ` Emanuel Berg
[not found] ` <mailman.966.1442016910.19560.help-gnu-emacs@gnu.org>
2015-09-12 2:01 ` Pascal J. Bourguignon
2015-09-12 3:26 ` Emanuel Berg
2015-09-13 7:50 ` tomas
2015-09-12 2:03 ` Pascal J. Bourguignon
2015-09-12 2:45 ` Stefan Monnier
2015-09-12 3:12 ` Emanuel Berg
2015-09-12 3:31 ` Emanuel Berg
[not found] ` <mailman.972.1442025961.19560.help-gnu-emacs@gnu.org>
2015-09-12 6:16 ` Pascal J. Bourguignon
2015-09-12 23:38 ` Emanuel Berg
2015-09-13 8:03 ` tomas
2015-09-14 1:31 ` Emanuel Berg
[not found] ` <mailman.1016.1442100597.19560.help-gnu-emacs@gnu.org>
2015-09-13 0:09 ` Pascal J. Bourguignon
2015-09-13 0:24 ` John Mastro
[not found] ` <mailman.1019.1442103883.19560.help-gnu-emacs@gnu.org>
2015-09-13 4:29 ` Pascal J. Bourguignon
2015-09-16 0:01 ` computer history (was: Re: member returns list) Emanuel Berg
[not found] ` <mailman.978.1442028310.19560.help-gnu-emacs@gnu.org>
2015-09-12 6:18 ` member returns list Pascal J. Bourguignon
2015-09-12 23:56 ` Emanuel Berg
[not found] ` <mailman.1018.1442101697.19560.help-gnu-emacs@gnu.org>
2015-09-13 0:20 ` Pascal J. Bourguignon
2015-09-14 1:24 ` Emanuel Berg
2015-09-12 2:04 ` Pascal J. Bourguignon
2015-09-12 3:15 ` Emanuel Berg
2015-09-12 7:40 ` Eli Zaretskii
[not found] ` <mailman.884.1441933051.19560.help-gnu-emacs@gnu.org>
2015-09-11 2:26 ` Pascal J. Bourguignon
2015-09-12 0:16 ` Emanuel Berg
2015-09-07 2:38 ` Drew Adams
2015-09-07 2:37 ` Drew Adams [this message]
[not found] ` <mailman.502.1441349470.19560.help-gnu-emacs@gnu.org>
2015-09-04 17:26 ` Barry Margolin
2015-09-05 17:40 ` Emanuel Berg
2015-09-02 0:40 ` member (was: Re: To `boundp' or not to `boundp'?) Emanuel Berg
[not found] ` <mailman.363.1441150201.19560.help-gnu-emacs@gnu.org>
2015-09-02 16:25 ` member returns list " Barry Margolin
2015-09-02 21:35 ` Emanuel Berg
[not found] ` <mailman.426.1441229773.19560.help-gnu-emacs@gnu.org>
2015-09-02 22:56 ` Barry Margolin
2015-09-02 23:23 ` Emanuel Berg
[not found] ` <mailman.368.1441153951.19560.help-gnu-emacs@gnu.org>
2015-09-03 5:19 ` member Pascal J. Bourguignon
2015-09-04 0:24 ` member Emanuel Berg
[not found] ` <<barmar-B5D67F.16201001092015@88-209-239-213.giganet.hu>
2015-09-01 20:42 ` To `boundp' or not to `boundp'? Drew Adams
2015-09-02 2:12 ` Stefan Monnier
2015-09-02 15:26 ` Alexander Shukaev
2015-09-02 16:51 ` Michael Heerdegen
[not found] ` <mailman.410.1441212753.19560.help-gnu-emacs@gnu.org>
2015-09-02 20:00 ` Barry Margolin
[not found] <mailman.719.1441763081.19560.help-gnu-emacs@gnu.org>
2015-09-09 15:03 ` member returns list Barry Margolin
2015-09-09 19:44 ` Ted Zlatanov
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=91d13d72-cc94-4a52-ab0a-15db05f82c73@default \
--to=drew.adams@oracle.com \
--cc=help-gnu-emacs@gnu.org \
--cc=pjb@informatimago.com \
/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).