comparison man/lispref/os.texi @ 4885:6772ce4d982b

Fix hash tables, #'member*, #'assoc*, #'eql compiler macros if bignums lisp/ChangeLog addition: 2010-01-24 Aidan Kehoe <kehoea@parhasard.net> Correct the semantics of #'member*, #'eql, #'assoc* in the presence of bignums; change the integerp byte code to fixnump semantics. * bytecomp.el (fixnump, integerp, byte-compile-integerp): Change the integerp byte code to fixnump; add a byte-compile method to integerp using fixnump and numberp and avoiding a funcall most of the time, since in the non-core contexts where integerp is used, it's mostly distinguishing between fixnums and things that are not numbers at all. * byte-optimize.el (side-effect-free-fns, byte-after-unbind-ops) (byte-compile-side-effect-and-error-free-ops): Replace the integerp bytecode with fixnump; add fixnump to the side-effect-free-fns. Add the other extended number type predicates to the list in passing. * obsolete.el (floatp-safe): Mark this as obsolete. * cl.el (eql): Go into more detail in the docstring here. Don't bother checking whether both arguments are numbers; one is enough, #'equal will fail correctly if they have distinct types. (subst): Replace a call to #'integerp (deciding whether to use #'memq or not) with one to #'fixnump. Delete most-positive-fixnum, most-negative-fixnum from this file; they're now always in C, so they can't be modified from Lisp. * cl-seq.el (member*, assoc*, rassoc*): Correct these functions in the presence of bignums. * cl-macs.el (cl-make-type-test): The type test for a fixnum is now fixnump. Ditch floatp-safe, use floatp instead. (eql): Correct this compiler macro in the presence of bignums. (assoc*): Correct this compiler macro in the presence of bignums. * simple.el (undo): Change #'integerp to #'fixnump here, since we use #'delq with the same value as ELT a few lines down. src/ChangeLog addition: 2010-01-24 Aidan Kehoe <kehoea@parhasard.net> Fix problems with #'eql, extended number types, and the hash table implementation; change the Bintegerp bytecode to fixnump semantics even on bignum builds, since #'integerp can have a fast implementation in terms of #'fixnump for most of its extant uses, but not vice-versa. * lisp.h: Always #include number.h; we want the macros provided in it, even if the various number types are not available. * number.h (NON_FIXNUM_NUMBER_P): New macro, giving 1 when its argument is of non-immediate number type. Equivalent to FLOATP if WITH_NUMBER_TYPES is not defined. * elhash.c (lisp_object_eql_equal, lisp_object_eql_hash): Use NON_FIXNUM_NUMBER_P in these functions, instead of FLOATP, giving more correct behaviour in the presence of the extended number types. * bytecode.c (Bfixnump, execute_optimized_program): Rename Bintegerp to Bfixnump; change its semantics to reflect the new name on builds with bignum support. * data.c (Ffixnump, Fintegerp, syms_of_data, vars_of_data): Always make #'fixnump available, even on non-BIGNUM builds; always implement #'integerp in this file, even on BIGNUM builds. Move most-positive-fixnum, most-negative-fixnum here from number.c, so they are Lisp constants even on builds without number types, and attempts to change or bind them error. Use the NUMBERP and INTEGERP macros even on builds without extended number types. * data.c (fixnum_char_or_marker_to_int): Rename this function from integer_char_or_marker_to_int, to better reflect the arguments it accepts. * number.c (Fevenp, Foddp, syms_of_number): Never provide #'integerp in this file. Remove #'oddp, #'evenp; their implementations are overridden by those in cl.el. * number.c (vars_of_number): most-positive-fixnum, most-negative-fixnum are no longer here. man/ChangeLog addition: 2010-01-23 Aidan Kehoe <kehoea@parhasard.net> Generally: be careful to say fixnum, not integer, when talking about fixed-precision integral types. I'm sure I've missed instances, both here and in the docstrings, but this is a decent start. * lispref/text.texi (Columns): Document where only fixnums, not integers generally, are accepted. (Registers): Remove some ancient char-int confoundance here. * lispref/strings.texi (Creating Strings, Creating Strings): Be more exact in describing where fixnums but not integers in general are accepted. (Creating Strings): Use a more contemporary example to illustrate how concat deals with lists including integers about #xFF. Delete some obsolete documentation on same. (Char Table Types): Document that only fixnums are accepted as values in syntax tables. * lispref/searching.texi (String Search, Search and Replace): Be exact in describing where fixnums but not integers in general are accepted. * lispref/range-tables.texi (Range Tables): Be exact in describing them; only fixnums are accepted to describe ranges. * lispref/os.texi (Killing XEmacs, User Identification) (Time of Day, Time Conversion): Be more exact about using fixnum where only fixed-precision integers are accepted. * lispref/objects.texi (Integer Type): Be more exact (and up-to-date) about the possible values for integers. Cross-reference to documentation of the bignum extension. (Equality Predicates): (Range Table Type): (Array Type): Use fixnum, not integer, to describe a fixed-precision integer. (Syntax Table Type): Correct some English syntax here. * lispref/numbers.texi (Numbers): Change the phrasing here to use fixnum to mean the fixed-precision integers normal in emacs. Document that our terminology deviates from that of Common Lisp, and that we're working on it. (Compatibility Issues): Reiterate the Common Lisp versus Emacs Lisp compatibility issues. (Comparison of Numbers, Arithmetic Operations): * lispref/commands.texi (Command Loop Info, Working With Events): * lispref/buffers.texi (Modification Time): Be more exact in describing where fixnums but not integers in general are accepted.
author Aidan Kehoe <kehoea@parhasard.net>
date Sun, 24 Jan 2010 15:21:27 +0000
parents aa5ed11f473b
children 1537701f08a1
comparison
equal deleted inserted replaced
4869:e533a9912ef1 4885:6772ce4d982b
417 killing XEmacs is @code{kill-emacs}. 417 killing XEmacs is @code{kill-emacs}.
418 418
419 @deffn Command kill-emacs &optional exit-data 419 @deffn Command kill-emacs &optional exit-data
420 This function exits the XEmacs process and kills it. 420 This function exits the XEmacs process and kills it.
421 421
422 If @var{exit-data} is an integer, then it is used as the exit status 422 If @var{exit-data} is a fixnum, then it is used as the exit status
423 of the XEmacs process. (This is useful primarily in batch operation; see 423 of the XEmacs process. (This is useful primarily in batch operation; see
424 @ref{Batch Mode}.) 424 @ref{Batch Mode}.)
425 425
426 If @var{exit-data} is a string, its contents are stuffed into the 426 If @var{exit-data} is a string, its contents are stuffed into the
427 terminal input buffer so that the shell (or whatever program next reads 427 terminal input buffer so that the shell (or whatever program next reads
763 is set, that value is used. Otherwise, if the environment variable 763 is set, that value is used. Otherwise, if the environment variable
764 @code{USER} is set, that value is used. Otherwise, the value is based 764 @code{USER} is set, that value is used. Otherwise, the value is based
765 on the effective @sc{uid}, not the real @sc{uid}. 765 on the effective @sc{uid}, not the real @sc{uid}.
766 766
767 If you specify @var{uid}, the value is the user name that corresponds 767 If you specify @var{uid}, the value is the user name that corresponds
768 to @var{uid} (which should be an integer). 768 to @var{uid} (which should be a fixnum).
769 769
770 @example 770 @example
771 @group 771 @group
772 (user-login-name) 772 (user-login-name)
773 @result{} "lewis" 773 @result{} "lewis"
882 additional information may be added at the end. 882 additional information may be added at the end.
883 883
884 @c Emacs 19 feature 884 @c Emacs 19 feature
885 The argument @var{time-value}, if given, specifies a time to format 885 The argument @var{time-value}, if given, specifies a time to format
886 instead of the current time. The argument should be a list whose first 886 instead of the current time. The argument should be a list whose first
887 two elements are integers. Thus, you can use times obtained from 887 two elements are fixnums. Thus, you can use times obtained from
888 @code{current-time} (see below) and from @code{file-attributes} 888 @code{current-time} (see below) and from @code{file-attributes}
889 (@pxref{File Attributes}). 889 (@pxref{File Attributes}).
890 890
891 @example 891 @example
892 @group 892 @group
933 If the operating system doesn't supply all the information necessary to 933 If the operating system doesn't supply all the information necessary to
934 compute the value, both elements of the list are @code{nil}. 934 compute the value, both elements of the list are @code{nil}.
935 935
936 The argument @var{time-value}, if given, specifies a time to analyze 936 The argument @var{time-value}, if given, specifies a time to analyze
937 instead of the current time. The argument should be a cons cell 937 instead of the current time. The argument should be a cons cell
938 containing two integers, or a list whose first two elements are 938 containing two fixnums, or a list whose first two elements are
939 integers. Thus, you can use times obtained from @code{current-time} 939 fixnums. Thus, you can use times obtained from @code{current-time}
940 (see above) and from @code{file-attributes} (@pxref{File Attributes}). 940 (see above) and from @code{file-attributes} (@pxref{File Attributes}).
941 @end defun 941 @end defun
942 942
943 @node Time Conversion 943 @node Time Conversion
944 @section Time Conversion 944 @section Time Conversion
945 945
946 These functions convert time values (lists of two or three integers) 946 These functions convert time values (lists of two or three fixnums)
947 to strings or to calendrical information. There is also a function to 947 to strings or to calendrical information. There is also a function to
948 convert calendrical information to a time value. You can get time 948 convert calendrical information to a time value. You can get time
949 values from the functions @code{current-time} (@pxref{Time of Day}) and 949 values from the functions @code{current-time} (@pxref{Time of Day}) and
950 @code{file-attributes} (@pxref{File Attributes}). 950 @code{file-attributes} (@pxref{File Attributes}).
951 951