GNU bug report logs -
#15021
24.3.50; `CL' manual: describe differences from Common Lisp, everywhere
Previous Next
Reported by: Drew Adams <drew.adams <at> oracle.com>
Date: Sun, 4 Aug 2013 17:54:02 UTC
Severity: minor
Tags: fixed
Merged with 15171
Found in version 24.3.50
Fixed in version 26.1
Done: Lars Ingebrigtsen <larsi <at> gnus.org>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 15021 in the body.
You can then email your comments to 15021 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#15021
; Package
emacs
.
(Sun, 04 Aug 2013 17:54:03 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Drew Adams <drew.adams <at> oracle.com>
:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org
.
(Sun, 04 Aug 2013 17:54:04 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
In general, some description is provided for the Emacs-Lisp versions of
CL things. But there is little or no info about how the Emacs version
of the thing differs from the CL version.
That missing info is one of the most important things to be documented.
Example of where we do point out a difference: In (cl) `Structures' we
say:
"In true Common Lisp, each structure type is a new type distinct from
all existing Lisp types. Since the underlying Emacs Lisp system
provides no way to create new distinct types, this package implements
structures as vectors (or lists upon request) with a special "tag"
symbol to identify them."
And there is more info about this type tag.
(Drop "true", BTW.)
But there are many more differences between what CL offers and what
package cl-lib provides. There needs to be much more documentation to
explain the differences. Otherwise, Emacs-Lisp users are forced to
examine the (dense and confusing) cl-lib.el code itself and guess what
the actual behavior is and how it differs from CL.
CL itself is specified rigorously and pretty completely. What is
missing is good Emacs-Lisp doc of just how cl-lib diverges from the CL
spec. Many (nearly all?) cl-lib functions, macros, whatever differ in
some way from CL, but little is said about these differences.
In GNU Emacs 24.3.50.1 (i686-pc-mingw32)
of 2013-08-02 on ODIEONE
Bzr revision: 113660 lekktu <at> gmail.com-20130802160313-rbi3o6322mz0m3ye
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
`configure --prefix=/c/Devel/emacs/binary --enable-checking=yes,glyphs
CFLAGS=-O0 -g3 LDFLAGS=-Lc:/Devel/emacs/lib
CPPFLAGS=-Ic:/Devel/emacs/include'
Merged 15021 15171.
Request was from
Lars Ingebrigtsen <larsi <at> gnus.org>
to
control <at> debbugs.gnu.org
.
(Sat, 08 Feb 2014 05:20:02 GMT)
Full text and
rfc822 format available.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#15021
; Package
emacs
.
(Fri, 29 Apr 2016 13:27:01 GMT)
Full text and
rfc822 format available.
Message #10 received at 15021 <at> debbugs.gnu.org (full text, mbox):
Lars Ingebrigtsen <larsi <at> gnus.org> writes:
> Drew Adams <drew.adams <at> oracle.com> writes:
>
>> This appendix is only a brief summary, it seems, and can be quite
>> misleading. I'm skeptical that it specifies "a list of all known
>> incompatibilities" between the Emacs cl* libraries and Common Lisp.
>>
>> But it is correct that it _should_ specify them all.
>
> Or we could just change the line "The following is a list of all known
> incompatibilities between this package and Common Lisp as documented in
> Steele" to "a list of some of the more glaring incompatibilities"...
I've now committed a similar wording.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
Added tag(s) fixed.
Request was from
Lars Ingebrigtsen <larsi <at> gnus.org>
to
control <at> debbugs.gnu.org
.
(Fri, 29 Apr 2016 13:27:02 GMT)
Full text and
rfc822 format available.
bug marked as fixed in version 25.2, send any further explanations to
15021 <at> debbugs.gnu.org and Drew Adams <drew.adams <at> oracle.com>
Request was from
Lars Ingebrigtsen <larsi <at> gnus.org>
to
control <at> debbugs.gnu.org
.
(Fri, 29 Apr 2016 13:27:02 GMT)
Full text and
rfc822 format available.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Sat, 28 May 2016 11:24:06 GMT)
Full text and
rfc822 format available.
bug unarchived.
Request was from
Glenn Morris <rgm <at> gnu.org>
to
control <at> debbugs.gnu.org
.
(Sun, 04 Dec 2016 02:50:04 GMT)
Full text and
rfc822 format available.
bug Marked as fixed in versions 26.1.
Request was from
Glenn Morris <rgm <at> gnu.org>
to
control <at> debbugs.gnu.org
.
(Sun, 04 Dec 2016 02:50:04 GMT)
Full text and
rfc822 format available.
bug No longer marked as fixed in versions 25.2.
Request was from
Glenn Morris <rgm <at> gnu.org>
to
control <at> debbugs.gnu.org
.
(Sun, 04 Dec 2016 02:50:04 GMT)
Full text and
rfc822 format available.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Sun, 01 Jan 2017 12:24:09 GMT)
Full text and
rfc822 format available.
This bug report was last modified 8 years and 173 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.