Mercurial > hg > xemacs-beta
view man/lispref/errors.texi @ 5307:c096d8051f89
Have NATNUMP give t for positive bignums; check limits appropriately.
src/ChangeLog addition:
2010-11-20 Aidan Kehoe <kehoea@parhasard.net>
* abbrev.c (Fexpand_abbrev):
* alloc.c:
* alloc.c (Fmake_list):
* alloc.c (Fmake_vector):
* alloc.c (Fmake_bit_vector):
* alloc.c (Fmake_byte_code):
* alloc.c (Fmake_string):
* alloc.c (vars_of_alloc):
* bytecode.c (UNUSED):
* bytecode.c (Fbyte_code):
* chartab.c (decode_char_table_range):
* cmds.c (Fself_insert_command):
* data.c (check_integer_range):
* data.c (Fnatnump):
* data.c (Fnonnegativep):
* data.c (Fstring_to_number):
* elhash.c (hash_table_size_validate):
* elhash.c (decode_hash_table_size):
* eval.c (Fbacktrace_frame):
* event-stream.c (lisp_number_to_milliseconds):
* event-stream.c (Faccept_process_output):
* event-stream.c (Frecent_keys):
* event-stream.c (Fdispatch_event):
* events.c (Fmake_event):
* events.c (Fevent_timestamp):
* events.c (Fevent_timestamp_lessp):
* events.h:
* events.h (struct command_builder):
* file-coding.c (gzip_putprop):
* fns.c:
* fns.c (check_sequence_range):
* fns.c (Frandom):
* fns.c (Fnthcdr):
* fns.c (Flast):
* fns.c (Fnbutlast):
* fns.c (Fbutlast):
* fns.c (Fmember):
* fns.c (Ffill):
* fns.c (Freduce):
* fns.c (replace_string_range_1):
* fns.c (Freplace):
* font-mgr.c (Ffc_pattern_get):
* frame-msw.c (msprinter_set_frame_properties):
* glyphs.c (check_valid_xbm_inline):
* indent.c (Fmove_to_column):
* intl-win32.c (mswindows_multibyte_to_unicode_putprop):
* lisp.h:
* lisp.h (ARRAY_DIMENSION_LIMIT):
* lread.c (decode_mode_1):
* mule-ccl.c (ccl_get_compiled_code):
* number.h:
* process-unix.c (unix_open_multicast_group):
* process.c (Fset_process_window_size):
* profile.c (Fstart_profiling):
* unicode.c (Funicode_to_char):
Change NATNUMP to return 1 for positive bignums; changes uses of
it and of CHECK_NATNUM appropriately, usually by checking for an
integer in an appropriate range.
Add array-dimension-limit and use it in #'make-vector,
#'make-string. Add array-total-size-limit, array-rank-limit while
we're at it, for the sake of any Common Lisp-oriented code that
uses these limits.
Rename check_int_range to check_integer_range, have it take
Lisp_Objects (and thus bignums) instead.
Remove bignum_butlast(), just set int_n to an appropriately large
integer if N is a bignum.
Accept bignums in check_sequence_range(), change the functions
that use check_sequence_range() appropriately.
Move the definition of NATNUMP() to number.h; document why it's a
reasonable name, contradicting an old comment.
tests/ChangeLog addition:
2010-11-20 Aidan Kehoe <kehoea@parhasard.net>
* automated/lisp-tests.el:
* automated/lisp-tests.el (featurep):
* automated/lisp-tests.el (wrong-type-argument):
* automated/mule-tests.el (featurep):
Check for args-out-of-range errors instead of wrong-type-argument
errors in various places when code is handed a large bignum
instead of a fixnum.
Also check for the wrong-type-argument errors when giving the same
code a non-integer value.
author | Aidan Kehoe <kehoea@parhasard.net> |
---|---|
date | Sat, 20 Nov 2010 16:49:11 +0000 |
parents | 576fb035e263 |
children |
line wrap: on
line source
@c -*-texinfo-*- @c This is part of the XEmacs Lisp Reference Manual. @c Copyright (C) 1990, 1991, 1992, 1993 Free Software Foundation, Inc. @c See the file lispref.texi for copying conditions. @setfilename ../../info/errors.info @node Standard Errors, Standard Buffer-Local Variables, Building XEmacs and Object Allocation, Top @appendix Standard Errors Here is the complete list of the error symbols in standard Emacs, grouped by concept. The list includes each symbol's message (on the @code{error-message} property of the symbol) and a cross reference to a description of how the error can occur. Each error symbol has an @code{error-conditions} property that is a list of symbols. Normally this list includes the error symbol itself and the symbol @code{error}. Occasionally it includes additional symbols, which are intermediate classifications, narrower than @code{error} but broader than a single error symbol. For example, all the errors in accessing files have the condition @code{file-error}. As a special exception, the error symbol @code{quit} does not have the condition @code{error}, because quitting is not considered an error. @xref{Errors}, for an explanation of how errors are generated and handled. @table @code @item @var{symbol} @var{string}; @var{reference}. @item error @code{"error"}@* @xref{Errors}. @item quit @code{"Quit"}@* @xref{Quitting}. @item args-out-of-range @code{"Args out of range"}@* @xref{Sequences Arrays Vectors}. @item arith-error @code{"Arithmetic error"}@* See @code{/} and @code{%} in @ref{Numbers}. @item beginning-of-buffer @code{"Beginning of buffer"}@* @xref{Motion}. @item buffer-read-only @code{"Buffer is read-only"}@* @xref{Read Only Buffers}. @item cyclic-function-indirection @code{"Symbol's chain of function indirections contains a loop"}@* @xref{Function Indirection}. @c XEmacs feature @item domain-error @code{"Arithmetic domain error"}@* @item end-of-buffer @code{"End of buffer"}@* @xref{Motion}. @item end-of-file @code{"End of file during parsing"}@* This is not a @code{file-error}.@* @xref{Input Functions}. @item file-error This error and its subcategories do not have error-strings, because the error message is constructed from the data items alone when the error condition @code{file-error} is present.@* @xref{Files}. @item file-locked This is a @code{file-error}.@* @xref{File Locks}. @item file-already-exists This is a @code{file-error}.@* @xref{Writing to Files}. @item file-supersession This is a @code{file-error}.@* @xref{Modification Time}. @item invalid-byte-code @code{"Invalid byte code"}@* @xref{Byte Compilation}. @item invalid-function @code{"Invalid function"}@* @xref{Classifying Lists}. @item invalid-read-syntax @code{"Invalid read syntax"}@* @xref{Input Functions}. @item invalid-regexp @code{"Invalid regexp"}@* @xref{Regular Expressions}. @c XEmacs feature @item mark-inactive @code{"The mark is not active now"}@* @item no-catch @code{"No catch for tag"}@* @xref{Catch and Throw}. @c XEmacs feature @item overflow-error @code{"Arithmetic overflow error"}@* @c XEmacs feature @item protected-field @code{"Attempt to modify a protected field"}@* @c XEmacs feature @item range-error @code{"Arithmetic range error"}@* @item search-failed @code{"Search failed"}@* @xref{Searching and Matching}. @item setting-constant @code{"Attempt to set a constant symbol"}@* @xref{Constant Variables, , Variables that Never Change}. @c XEmacs feature @item singularity-error @code{"Arithmetic singularity error"}@* @c XEmacs feature @item tooltalk-error @code{"ToolTalk error"}@* @xref{ToolTalk Support}. @c XEmacs feature @item undefined-keystroke-sequence @code{"Undefined keystroke sequence"}@* @ignore FSF Emacs only @item undefined-color @code{"Undefined color"}@* @xref{Color Names}. @end ignore @item void-function @code{"Symbol's function definition is void"}@* @xref{Function Cells}. @item void-variable @code{"Symbol's value as variable is void"}@* @xref{Accessing Variables}. @item wrong-number-of-arguments @code{"Wrong number of arguments"}@* @xref{Classifying Lists}. @item wrong-type-argument @code{"Wrong type argument"}@* @xref{Type Predicates}. @end table These error types, which are all classified as special cases of @code{arith-error}, can occur on certain systems for invalid use of mathematical functions. @table @code @item domain-error @code{"Arithmetic domain error"}@* @xref{Math Functions}. @item overflow-error @code{"Arithmetic overflow error"}@* @xref{Math Functions}. @item range-error @code{"Arithmetic range error"}@* @xref{Math Functions}. @item singularity-error @code{"Arithmetic singularity error"}@* @xref{Math Functions}. @item underflow-error @code{"Arithmetic underflow error"}@* @xref{Math Functions}. @end table