Mercurial > hg > xemacs-beta
annotate man/lispref/index.texi @ 5911:48386fd60fd0
GMP functions that take doubles choke on non-finite values, avoid that.
src/ChangeLog addition:
2015-05-10 Aidan Kehoe <kehoea@parhasard.net>
* floatfns.c (double_to_integer):
Rename this from float_to_int to fit our newer, bignum-compatible
terminology.
GMP can signal SIGFPE when asked to turn NaN or infinity into a
bignum, and we're not prepared to handle that signal if the OS float
library routines don't do that, so check for those values
explicitly.
* floatfns.c (ceiling_two_float):
* floatfns.c (ceiling_one_float):
* floatfns.c (floor_two_float):
* floatfns.c (floor_one_float):
* floatfns.c (round_two_float):
* floatfns.c (round_one_float):
* floatfns.c (truncate_two_float):
* floatfns.c (truncate_one_float):
Call double_to_integer() with its new name.
* number.c:
Don't use the {bignum,ratio,bigfloat}_set_double functions
directly here, with GMP they can choke when handed non-finite C
doubles, call Ftruncate() and the new float_to_bigfloat() from
floatfns.c. Maybe we should extend number-gmp.c with GMP-specific
implementations that check for non-finite values.
tests/ChangeLog addition:
2015-05-10 Aidan Kehoe <kehoea@parhasard.net>
* automated/lisp-tests.el:
Backslash a few parentheses in the first column for the sake of
fontification.
* automated/lisp-tests.el:
Check that the rounding functions signal Lisp errors correctly
when handed positive and negative infinity and NaN.
author | Aidan Kehoe <kehoea@parhasard.net> |
---|---|
date | Sun, 10 May 2015 19:07:09 +0100 |
parents | 576fb035e263 |
children |
rev | line source |
---|---|
398 | 1 @c -*-texinfo-*- |
2 @setfilename ../../info/index.info | |
3 | |
4 @c Indexing guidelines | |
5 | |
6 @c I assume that all indexes will be combined. | |
7 @c Therefore, if a generated findex and permutations | |
8 @c cover the ways an index user would look up the entry, | |
9 @c then no cindex is added. | |
10 @c Concept index (cindex) entries will also be permuted. Therefore, they | |
11 @c have no commas and few irrelevant connectives in them. | |
12 | |
13 @c I tried to include words in a cindex that give the context of the entry, | |
14 @c particularly if there is more than one entry for the same concept. | |
15 @c For example, "nil in keymap" | |
16 @c Similarly for explicit findex and vindex entries, e.g. "print example". | |
17 | |
18 @c Error codes are given cindex entries, e.g. "end-of-file error". | |
19 | |
20 @c pindex is used for .el files and Unix programs | |
21 | |
22 @node Index, , Standard Hooks, Top | |
23 @unnumbered Index | |
24 | |
25 @ignore | |
26 All variables, functions, keys, programs, files, and concepts are | |
444 | 27 in this one index. |
398 | 28 |
29 All names and concepts are permuted, so they appear several times, one | |
30 for each permutation of the parts of the name. For example, | |
31 @code{function-name} would appear as @b{function-name} and @b{name, | |
32 function-}. Key entries are not permuted, however. | |
33 @end ignore | |
34 | |
35 @c Print the indices | |
36 | |
37 @printindex fn |