From: Michael Witten <mfwitten@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: 11862@debbugs.gnu.org, Wolfgang Jenkner <wjenkner@inode.at>,
Richard Stallman <rms@gnu.org>
Subject: bug#11862: [PATCH 8a/9] doc/lispref/intro.texi: Introduce the term `value' early on
Date: Fri, 06 Jul 2012 20:17:05 -0000 [thread overview]
Message-ID: <0176eb16f5a643f89eb12633f213a542-mfwitten@gmail.com> (raw)
In-Reply-To: <31927313f03b410aaa9830427ff3a0c1-mfwitten@gmail.com>
The term `value' is used pervasively, so it should be brought to
the reader's attention early on; it is introduced in node `Some Terms'.
Originally, `doc/lispref/functions.texi' introduced both `@dfn{value}'
and `@dfn{return value}' in describing the result of a computation,
but now only `return value' is marked with `@dfn'.
---
doc/lispref/functions.texi | 2 +-
doc/lispref/intro.texi | 9 +++++----
2 files changed, 6 insertions(+), 5 deletions(-)
diff --git a/doc/lispref/functions.texi b/doc/lispref/functions.texi
index ab2789b..b0eea05 100644
--- a/doc/lispref/functions.texi
+++ b/doc/lispref/functions.texi
@@ -37,7 +37,7 @@ define them.
@cindex argument
In a general sense, a function is a rule for carrying out a
computation given input values called @dfn{arguments}. The result of
-the computation is called the @dfn{value} or @dfn{return value} of the
+the computation is called the @dfn{return value} (or the ``value'') of the
function. The computation can also have side effects, such as lasting
changes in the values of variables or the contents of data structures.
diff --git a/doc/lispref/intro.texi b/doc/lispref/intro.texi
index 5ca4d37..0766a23 100644
--- a/doc/lispref/intro.texi
+++ b/doc/lispref/intro.texi
@@ -147,10 +147,11 @@ manual. You may want to skip this section and refer back to it later.
Throughout this manual, the phrases ``the Lisp reader'' and ``the Lisp
printer'' refer to those routines in Lisp that convert textual
representations of Lisp objects into actual Lisp objects, and vice
-versa. @xref{Printed Representation}, for more details. You, the
-person reading this manual, are thought of as ``the programmer'' and are
-addressed as ``you''. ``The user'' is the person who uses Lisp
-programs, including those you write.
+versa. @xref{Printed Representation}, for more details. A Lisp object
+is commonly referred to as a @dfn{value}. You, the person reading this
+manual, are thought of as ``the programmer'' and are addressed as ``you''.
+``The user'' is the person who uses Lisp programs, including those you
+write.
@cindex typographic conventions
Examples of Lisp code are formatted like this: @code{(list 1 2 3)}.
--
1.7.11.1.29.gf71be5c
next prev parent reply other threads:[~2012-07-06 20:17 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-04 20:15 bug#11862: [PATCH 0/9] doc/lispref/intro.texi: Copyediting Michael Witten
2012-07-04 20:15 ` bug#11862: [PATCH 1/9] doc/lispref/intro.texi: Offset modifier with a comma Michael Witten
2012-07-05 10:13 ` Richard Stallman
2012-07-05 16:52 ` bug#11862: [PATCH 1/9] doc/lispref/intro.texi: Offset modifier Michael Witten
2012-07-04 20:15 ` bug#11862: [PATCH 2/9] doc/lispref/intro.texi: `can' -> `may' Michael Witten
2012-07-05 10:13 ` Richard Stallman
2012-07-04 20:15 ` bug#11862: [PATCH 3/9] doc/lispref/intro.texi: Eradicate that pesky future tense Michael Witten
2012-07-05 10:13 ` Richard Stallman
2012-07-04 20:15 ` bug#11862: [PATCH 4/9] doc/lispref/intro.texi: More precise language Michael Witten
2012-07-05 10:13 ` Richard Stallman
2012-07-04 20:15 ` bug#11862: [PATCH 5/9] doc/lispref/intro.texi: Use singular form in a sentence Michael Witten
2012-07-04 20:15 ` bug#11862: [PATCH 6/9] doc/lispref/intro.texi: Re-fill a paragraph Michael Witten
2012-07-04 20:15 ` bug#11862: [PATCH 7/9] doc/lispref/intro.texi: `optional' -> `&optional'; Michael Witten
2012-07-05 3:03 ` Glenn Morris
2012-07-04 20:15 ` bug#11862: [PATCH 8/9] doc/lispref/intro.texi: More precise language for Michael Witten
2012-07-05 21:50 ` Richard Stallman
2012-07-05 22:55 ` bug#11862: [PATCH 8/9 v2] doc/lispref/intro.texi: More precise language for what a variable is Michael Witten
2012-07-06 1:58 ` bug#11862: [PATCH 8/9 v2] doc/lispref/intro.texi: More preciselanguage " Drew Adams
2012-07-06 8:07 ` bug#11862: [PATCH 8/9 v3] doc/lispref/intro.texi: More precise language " Michael Witten
2012-07-06 15:55 ` Wolfgang Jenkner
2012-07-06 16:45 ` Drew Adams
2012-07-06 20:06 ` bug#11862: Splitting and simplifying [PATCH 8/9] Michael Witten
2012-07-06 20:17 ` Michael Witten [this message]
2012-07-06 20:18 ` bug#11862: [PATCH 8b/2] doc/lispref/intro.texi: Reduce and reorganize node `A sample Variable Description' Michael Witten
2012-07-07 9:18 ` bug#11862: [PATCH 8/9 v3] doc/lispref/intro.texi: More precise language for what a variable is Richard Stallman
2012-07-08 4:41 ` bug#11862: [Copyright assignment] Chong Yidong
2012-07-06 6:40 ` bug#11862: [PATCH 8/9 v2] doc/lispref/intro.texi: More precise language for what a variable is Eli Zaretskii
2012-07-04 20:16 ` bug#11862: [PATCH 9/9] doc/lispref/intro.texi: Use passive voice Michael Witten
2012-07-05 10:14 ` Richard Stallman
2012-07-05 14:04 ` Stephen Berman
2012-07-05 16:37 ` Eli Zaretskii
2012-07-05 16:59 ` Glenn Morris
2012-07-05 17:14 ` Michael Witten
2012-07-05 19:09 ` Stephen Berman
2012-07-05 2:52 ` bug#11862: [PATCH 0/9] doc/lispref/intro.texi: Copyediting Stefan Monnier
[not found] ` <CAMOZ1BsRkioUhGGOuFrmbkMRnJiQ6h=tviNODS11BjG3_jYVbA@mail.gmail.com>
2012-07-05 7:09 ` Glenn Morris
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=0176eb16f5a643f89eb12633f213a542-mfwitten@gmail.com \
--to=mfwitten@gmail.com \
--cc=11862@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=rms@gnu.org \
--cc=wjenkner@inode.at \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).