Mercurial > hg > xemacs-beta
diff man/lispref/objects.texi @ 5374:d967d96ca043
Conditionalise the old-* functions and byte codes at compile time.
src/ChangeLog addition:
2011-03-15 Aidan Kehoe <kehoea@parhasard.net>
* config.h.in (SUPPORT_CONFOUNDING_FUNCTIONS): New #define,
equivalent NEED_TO_HANDLE_21_4_CODE by default, describing whether
this XEmacs should support the old-eq, old-equal and related
functions and byte codes.
* bytecode.c (UNUSED):
Only interpret old-eq, old-equal, old-memq if
SUPPORT_CONFOUNDING_FUNCTIONS is defined.
* data.c:
Move Fold_eq to fns.c with the rest of the Fold_* functions.
* fns.c:
* fns.c (Fmemq):
* fns.c (memq_no_quit):
* fns.c (assoc_no_quit):
* fns.c (Frassq):
* fns.c (Fequal):
* fns.c (Fold_equal):
* fns.c (syms_of_fns):
Group old-eq, old-equal, old-memq etc together, surround them with
#ifdef SUPPORT_CONFOUNDING_FUNCTIONS.
lisp/ChangeLog addition:
2011-03-15 Aidan Kehoe <kehoea@parhasard.net>
* bytecomp.el:
Don't generate the old-eq, old-memq, old-equal bytecodes any more,
but keep the information about them around for the sake of the
disassembler.
man/ChangeLog addition:
2011-03-15 Aidan Kehoe <kehoea@parhasard.net>
* lispref/objects.texi (Character Type):
* lispref/objects.texi (Equality Predicates):
No longer document `old-eq', `old-equal', they haven't been used
in years.
tests/ChangeLog addition:
2011-03-17 Aidan Kehoe <kehoea@parhasard.net>
* automated/lisp-tests.el:
Only test the various old-* function if old-eq is bound and a
subr.
| author | Aidan Kehoe <kehoea@parhasard.net> |
|---|---|
| date | Thu, 17 Mar 2011 20:13:00 +0000 |
| parents | f5a5501814f5 |
| children | 9fae6227ede5 |
line wrap: on
line diff
--- a/man/lispref/objects.texi Mon Mar 14 21:04:45 2011 +0000 +++ b/man/lispref/objects.texi Thu Mar 17 20:13:00 2011 +0000 @@ -349,19 +349,6 @@ primitive types. (This change was necessary in order for @sc{mule}, i.e. Asian-language, support to be correctly implemented.) - Even in XEmacs version 20, remnants of the equivalence between -characters and integers still exist; this is termed the @dfn{char-int -confoundance disease}. In particular, many functions such as @code{eq}, -@code{equal}, and @code{memq} have equivalent functions (@code{old-eq}, -@code{old-equal}, @code{old-memq}, etc.) that pretend like characters -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 -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. - Every character has an equivalent integer, called the @dfn{character code}. For example, the character @kbd{A} is represented as the @w{integer 65}, following the standard @sc{ascii} representation of @@ -2317,32 +2304,6 @@ @end defun -@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 -equivalent integer, even though the objects are of different types! -You should @emph{not} ever call this function explicitly in your -code. However, be aware that all calls to @code{eq} in byte code -compiled under version 19 map to @code{old-eq} in XEmacs 20. -(Likewise for @code{old-equal}, @code{old-memq}, @code{old-member}, -@code{old-assq} and @code{old-assoc}.) - -@example -@group -;; @r{Remember, this does not apply under XEmacs 19.} -?A - @result{} ?A -(char-int ?A) - @result{} 65 -(old-eq ?A 65) - @result{} t ; @r{Eek, we've been infected.} -(eq ?A 65) - @result{} nil ; @r{We are still healthy.} -@end group -@end example -@end defun - @defun eql object1 object2 This function returns @code{t} if the two arguments are the same object,