comparison man/lispref/objects.texi @ 444:576fb035e263 r21-2-37

Import from CVS: tag r21-2-37
author cvs
date Mon, 13 Aug 2007 11:36:19 +0200
parents 8de8e3f6228a
children b05e2a249757
comparison
equal deleted inserted replaced
443:a8296e22da4e 444:576fb035e263
1079 @noindent 1079 @noindent
1080 where @var{property-data} consists of zero or more elements, in groups 1080 where @var{property-data} consists of zero or more elements, in groups
1081 of three as follows: 1081 of three as follows:
1082 1082
1083 @example 1083 @example
1084 @var{beg} @var{end} @var{plist} 1084 @var{start} @var{end} @var{plist}
1085 @end example 1085 @end example
1086 1086
1087 @noindent 1087 @noindent
1088 The elements @var{beg} and @var{end} are integers, and together specify 1088 The elements @var{start} and @var{end} are integers, and together specify
1089 a range of indices in the string; @var{plist} is the property list for 1089 a range of indices in the string; @var{plist} is the property list for
1090 that range. 1090 that range.
1091 @end ignore 1091 @end ignore
1092 1092
1093 @xref{Strings and Characters}, for functions that work on strings. 1093 @xref{Strings and Characters}, for functions that work on strings.
2253 @end group 2253 @end group
2254 @end example 2254 @end example
2255 2255
2256 @end defun 2256 @end defun
2257 2257
2258 @defun old-eq obj1 obj2 2258 @defun old-eq object1 object2
2259 This function exists under XEmacs 20 and is exactly like @code{eq} 2259 This function exists under XEmacs 20 and is exactly like @code{eq}
2260 except that it suffers from the char-int confoundance disease. 2260 except that it suffers from the char-int confoundance disease.
2261 In other words, it returns @code{t} if given a character and the 2261 In other words, it returns @code{t} if given a character and the
2262 equivalent integer, even though the objects are of different types! 2262 equivalent integer, even though the objects are of different types!
2263 You should @emph{not} ever call this function explicitly in your 2263 You should @emph{not} ever call this function explicitly in your