One quick thing. Kent Pitman has recomended that people stop referencing
CLtL1 and CLtL2 and instead reference the ansi spec. Since that is quite
expensive the next best thing online is the HyperSpec:
http://www.harlequin.com/education/books/HyperSpec/FrontMatter/index.html
I know that CLtLn make for good toilet reading, but its not a representation
of the official spec.
You may now return to your normal discourse.
-Reggie
-----Original Message-----
From: owner-xemacs-beta(a)xemacs.org
[mailto:owner-xemacs-betaï¼ xemacs.org]On Behalf Of Jerry James
Sent: Monday, July 13, 1998 5:44 PM
To: xemacs-beta(a)xemacs.org
Subject: Re: scheme - my opinion
On Mon, 13 Jul 1998 at 13:23:59 +0900 (JST), "Stephen J. Turnbull"
<turnbull(a)sk.tsukuba.ac.jp> wrote:
Hmm. Sounds like Common Lisp is going to require lots of extensions
to be useful to us, to me. CLtL1, at least, makes no reference to
editing buffers or multilingual text processing, frames or extents.
Also, it seems possible to me that Common Lisp specifies some things
we would rather be free to implement in our own way (doesn't CL
specify the use of bucky bits and fonts in character representation,
or did that go away?---I can't find the passage I'm sure I remember in
CLtL1, sorry if this is misinformed).
<delurk>
Doesn't CLISP include some CLtL2 constructs? I seem to remember that it
does. In that case, rather than sifting through the large CLtL1, you
may need to dig through the enormous CLtL2. Fortunately for those of us
who don't want to buy a copy, it can be accessed online here:
<
URL:http://www.cs.cmu.edu/Groups/AI/html/cltl/cltl2.html>
The part about bits and fonts you mentioned above was removed for CLtL2,
as documented here:
<
URL:http://www.cs.cmu.edu/Groups/AI/html/cltl/clm/node25.html>
I don't know whether CLISP follows CLtL1 or CLtL2 in this case.
</delurk>
--
Jerry James
Email: jerry(a)cs.ucsb.edu
WWW:
http://www.cs.ucsb.edu/~jerry/