From: Richard Stallman <rms@gnu.org>
To: Jean-Christophe Helary <jean.christophe.helary@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Terminology question
Date: Tue, 26 Apr 2016 21:58:15 -0400 [thread overview]
Message-ID: <E1avEk3-0005cp-MI@fencepost.gnu.org> (raw)
In-Reply-To: <EA499A67-6C56-425E-BCDA-5CDB3A82D871@gmail.com> (message from Jean-Christophe Helary on Tue, 26 Apr 2016 19:20:15 +0900)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> I cannot find a clear definition of "form", "expression", "symbolic expression", "sexp" and whether the terms are equivalent or not.
I think "form" and "expression" are synonymous; both mean a Lisp object
meant for evaluatoin.
"Sexp" generally refers to text rather than Lisp objets as such. It
means the textual representation of one object (including nested
objects).
> In chapter 9.1 there is "A Lisp object that is intended for
> evaluation is called a form or expression[4]." It is not clear
> what a Lisp obect not intended for evaluation is.
I don't understand that question. Every Lisp object is either
intended for evaluation or not. If it is intended for evaluation,
it is an expression (form).
It would be good to go through the manual to make this consistent and
clear.
--
Dr Richard Stallman
President, Free Software Foundation (gnu.org, fsf.org)
Internet Hall-of-Famer (internethalloffame.org)
Skype: No way! See stallman.org/skype.html.
prev parent reply other threads:[~2016-04-27 1:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-26 10:20 Terminology question Jean-Christophe Helary
2016-04-26 14:48 ` John Wiegley
2016-04-27 4:05 ` Jean-Christophe Helary
2016-04-27 12:46 ` Stefan Monnier
2016-04-27 1:58 ` Richard Stallman [this message]
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=E1avEk3-0005cp-MI@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jean.christophe.helary@gmail.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.