Mercurial > hg > xemacs-beta
comparison man/lispref/objects.texi @ 440:8de8e3f6228a r21-2-28
Import from CVS: tag r21-2-28
| author | cvs |
|---|---|
| date | Mon, 13 Aug 2007 11:33:38 +0200 |
| parents | 3ecd8885ac67 |
| children | 576fb035e263 |
comparison
equal
deleted
inserted
replaced
| 439:357dd071b03c | 440:8de8e3f6228a |
|---|---|
| 361 @code{equal}, and @code{memq} have equivalent functions (@code{old-eq}, | 361 @code{equal}, and @code{memq} have equivalent functions (@code{old-eq}, |
| 362 @code{old-equal}, @code{old-memq}, etc.) that pretend like characters | 362 @code{old-equal}, @code{old-memq}, etc.) that pretend like characters |
| 363 are integers are the same. Byte code compiled under any version 19 | 363 are integers are the same. Byte code compiled under any version 19 |
| 364 Emacs will have all such functions mapped to their @code{old-} equivalents | 364 Emacs will have all such functions mapped to their @code{old-} equivalents |
| 365 when the byte code is read into XEmacs 20. This is to preserve | 365 when the byte code is read into XEmacs 20. This is to preserve |
| 366 compatibility -- Emacs 19 converts all constant characters to the equivalent | 366 compatibility---Emacs 19 converts all constant characters to the equivalent |
| 367 integer during byte-compilation, and thus there is no other way to preserve | 367 integer during byte-compilation, and thus there is no other way to preserve |
| 368 byte-code compatibility even if the code has specifically been written | 368 byte-code compatibility even if the code has specifically been written |
| 369 with the distinction between characters and integers in mind. | 369 with the distinction between characters and integers in mind. |
| 370 | 370 |
| 371 Every character has an equivalent integer, called the @dfn{character | 371 Every character has an equivalent integer, called the @dfn{character |
| 372 code}. For example, the character @kbd{A} is represented as the | 372 code}. For example, the character @kbd{A} is represented as the |
| 373 @w{integer 65}, following the standard @sc{ascii} representation of | 373 @w{integer 65}, following the standard @sc{ascii} representation of |
| 374 characters. If XEmacs was not compiled with @sc{mule} support, the | 374 characters. If XEmacs was not compiled with @sc{mule} support, the |
| 375 range of this integer will always be 0 to 255 -- eight bits, or one | 375 range of this integer will always be 0 to 255---eight bits, or one |
| 376 byte. (Integers outside this range are accepted but silently truncated; | 376 byte. (Integers outside this range are accepted but silently truncated; |
| 377 however, you should most decidedly @emph{not} rely on this, because it | 377 however, you should most decidedly @emph{not} rely on this, because it |
| 378 will not work under XEmacs with @sc{mule} support.) When @sc{mule} | 378 will not work under XEmacs with @sc{mule} support.) When @sc{mule} |
| 379 support is present, the range of character codes is much | 379 support is present, the range of character codes is much |
| 380 larger. (Currently, 19 bits are used.) | 380 larger. (Currently, 19 bits are used.) |