GNU bug report logs -
#49785
[DOC] About Lisp Data Types
Previous Next
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 49785 in the body.
You can then email your comments to 49785 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#49785
; Package
emacs
.
(Fri, 30 Jul 2021 18:53:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Kevin Vigouroux <ke.vigouroux <at> laposte.net>
:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org
.
(Fri, 30 Jul 2021 18:53:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
Some expressions about data types are convoluted or could be more
expressive.
[[info:elisp#Some Terms]]
[...] that convert textual representations of Lisp objects into
actual Lisp objects, and vice versa.
[[info:elisp#Lisp Data Types]]
Objects of the same type have similar structures and may usually be
used in the same contexts.
[...] the primitive type of each object is implicit in the object
itself.
[...] Such type declarations do not exist in Emacs Lisp. A Lisp
variable can have any type of value, and it remembers whatever value
you store in it, type and all.
I would have phrased it differently.
“The representation of a Lisp program is fundamental. At a high level,
the operation of the program is represented by its components. At a low
level, a Lisp program is a collection of routines which process data
found in the source files. Globally, a Lisp program is a set of
expressions formed with objects: data structures, lists and symbols.”
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#49785
; Package
emacs
.
(Sat, 31 Jul 2021 11:19:01 GMT)
Full text and
rfc822 format available.
Message #8 received at 49785 <at> debbugs.gnu.org (full text, mbox):
Kevin Vigouroux <ke.vigouroux <at> laposte.net> writes:
> I would have phrased it differently.
>
> “The representation of a Lisp program is fundamental. At a high level,
> the operation of the program is represented by its components. At a low
> level, a Lisp program is a collection of routines which process data
> found in the source files. Globally, a Lisp program is a set of
> expressions formed with objects: data structures, lists and symbols.”
Sorry; I don't see any problems with the original text, and I don't
think the proposed text explains anything much to people who are
interested in what Emacs Lisp is.
Closing.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
Added tag(s) notabug.
Request was from
Lars Ingebrigtsen <larsi <at> gnus.org>
to
control <at> debbugs.gnu.org
.
(Sat, 31 Jul 2021 11:19:01 GMT)
Full text and
rfc822 format available.
bug closed, send any further explanations to
49785 <at> debbugs.gnu.org and Kevin Vigouroux <ke.vigouroux <at> laposte.net>
Request was from
Lars Ingebrigtsen <larsi <at> gnus.org>
to
control <at> debbugs.gnu.org
.
(Sat, 31 Jul 2021 11:19:02 GMT)
Full text and
rfc822 format available.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#49785
; Package
emacs
.
(Sat, 31 Jul 2021 16:47:02 GMT)
Full text and
rfc822 format available.
Message #15 received at 49785 <at> debbugs.gnu.org (full text, mbox):
It is written in black on white: we explain what constitutes a Lisp
program using the syntax as a thread.
[[info:elisp#Lisp Data Types]]
This chapter describes the purpose, printed representation and read
syntax of each of the standard types in GNU Emacs Lisp.
The problem is that it's not well presented. What is the link between a
variable, objects, what can be displayed and the Lisp syntax?
Nothing.
Best Regards,
Kevin Vigouroux
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Sun, 29 Aug 2021 11:24:08 GMT)
Full text and
rfc822 format available.
This bug report was last modified 2 years and 213 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.