summaryrefslogtreecommitdiff
path: root/lispref/symbols.texi
diff options
context:
space:
mode:
authorKarl Heuer <kwzh@gnu.org>1995-06-06 19:21:15 +0000
committerKarl Heuer <kwzh@gnu.org>1995-06-06 19:21:15 +0000
commitbfe721d172158ccdcd925e55f5a658421ca0d4fe (patch)
tree2d2882c335a04acb20662d2b5aa6dc2246a6f0aa /lispref/symbols.texi
parent5c4276bc6de449d416cc83dd034892da66badcb7 (diff)
downloademacs-bfe721d172158ccdcd925e55f5a658421ca0d4fe.tar.gz
*** empty log message ***
Diffstat (limited to 'lispref/symbols.texi')
-rw-r--r--lispref/symbols.texi17
1 files changed, 9 insertions, 8 deletions
diff --git a/lispref/symbols.texi b/lispref/symbols.texi
index caba9a9bd7e..1921dec922c 100644
--- a/lispref/symbols.texi
+++ b/lispref/symbols.texi
@@ -151,7 +151,8 @@ expression and storing it in the function cell of the symbol. This
lambda expression thus becomes the function definition of the symbol.
(The term ``function definition'', meaning the contents of the function
cell, is derived from the idea that @code{defun} gives the symbol its
-definition as a function.) @xref{Functions}.
+definition as a function.) @code{defsubst} and @code{defalias} are two
+other ways of defining a function. @xref{Functions}.
@code{defmacro} defines a symbol as a macro. It creates a macro
object and stores it in the function cell of the symbol. Note that a
@@ -160,8 +161,8 @@ both macro and function definitions are kept in the function cell, and
that cell can hold only one Lisp object at any given time.
@xref{Macros}.
- In GNU Emacs Lisp, a definition is not required in order to use a
-symbol as a variable or function. Thus, you can make a symbol a global
+ In Emacs Lisp, a definition is not required in order to use a symbol
+as a variable or function. Thus, you can make a symbol a global
variable with @code{setq}, whether you define it first or not. The real
purpose of definitions is to guide programmers and programming tools.
They inform programmers who read the code that certain symbols are
@@ -503,11 +504,11 @@ stored in the property list @var{plist}. For example,
@end defun
@defun plist-put plist property value
-This stores @var{value} as the value of the @var{property} property
-stored in the property list @var{plist}. It may modify @var{plist}
-destructively, or it may construct new list structure without altering
-the old. The function returns the modified property list, so you can
-store that back in the place where you got @var{plist}. For example,
+This stores @var{value} as the value of the @var{property} property in
+the property list @var{plist}. It may modify @var{plist} destructively,
+or it may construct new list structure without altering the old. The
+function returns the modified property list, so you can store that back
+in the place where you got @var{plist}. For example,
@example
(setq my-plist '(bar t foo 4))