This commit was generated by cvs2svn to compensate for changes in r9048,

[chise/xemacs-chise.git.1] / man / lispref / objects.texi

diff --git a/man/lispref/objects.texi b/man/lispref/objects.texi
index a809171..4835d1c 100644 (file)
--- a/man/lispref/objects.texi
+++ b/man/lispref/objects.texi
@@ -3,7 +3,7 @@
 @c Copyright (C) 1990, 1991, 1992, 1993, 1994 Free Software Foundation, Inc.
 @c See the file lispref.texi for copying conditions.
 @setfilename ../../info/objects.info
-@node Lisp Data Types, Numbers, Introduction, Top
+@node Lisp Data Types, Numbers, Packaging, Top
 @chapter Lisp Data Types
 @cindex object
 @cindex Lisp object
@@ -363,7 +363,7 @@ confoundance disease}.  In particular, many functions such as @code{eq},
 are integers are the same.  Byte code compiled under any version 19
 Emacs will have all such functions mapped to their @code{old-} equivalents
 when the byte code is read into XEmacs 20.  This is to preserve
-compatibility -- Emacs 19 converts all constant characters to the equivalent
+compatibility---Emacs 19 converts all constant characters to the equivalent
 integer during byte-compilation, and thus there is no other way to preserve
 byte-code compatibility even if the code has specifically been written
 with the distinction between characters and integers in mind.
@@ -372,7 +372,7 @@ with the distinction between characters and integers in mind.
 code}.  For example, the character @kbd{A} is represented as the
 @w{integer 65}, following the standard @sc{ascii} representation of
 characters.  If XEmacs was not compiled with @sc{mule} support, the
-range of this integer will always be 0 to 255 -- eight bits, or one
+range of this integer will always be 0 to 255---eight bits, or one
 byte. (Integers outside this range are accepted but silently truncated;
 however, you should most decidedly @emph{not} rely on this, because it
 will not work under XEmacs with @sc{mule} support.)  When @sc{mule}
@@ -1081,11 +1081,11 @@ where @var{property-data} consists of zero or more elements, in groups
 of three as follows:
 
 @example
-@var{beg} @var{end} @var{plist}
+@var{start} @var{end} @var{plist}
 @end example
 
 @noindent
-The elements @var{beg} and @var{end} are integers, and together specify
+The elements @var{start} and @var{end} are integers, and together specify
 a range of indices in the string; @var{plist} is the property list for
 that range.
 @end ignore
@@ -2255,7 +2255,7 @@ to @code{old-eq} when executed under XEmacs 20.
 
 @end defun
 
-@defun old-eq obj1 obj2
+@defun old-eq object1 object2
 This function exists under XEmacs 20 and is exactly like @code{eq}
 except that it suffers from the char-int confoundance disease.
 In other words, it returns @code{t} if given a character and the