Mercurial > hg > xemacs-beta
view info/dir @ 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 | c2580215c222 |
| children |
line wrap: on
line source
-*- Text -*- This is the file .../info/dir, which contains the topmost node of the Info hierarchy. The first time you invoke Info you start off looking at that node, which is (dir)Top. Rather than adding new nodes to this directory (and this file) it is a better idea to put them in a site-local directory, and then configure info to search in that directory as well. That way, you won't have to re-edit this file when a new release of the editor comes out. For example, you could add this code to .../lisp/site-start.el, which is loaded before ~/.emacs each time the editor starts up: ;; find local info nodes (setq Info-directory-list (append Info-directory-list '("/private/info/"))) Then, when you enter info, a dir file like this one will be automatically created and saved (provided you have write access to the directory). The contents of that file "/private/info/dir" will be appended to the contents of this file. File: dir Node: Top This is the top of the INFO tree This is Info, the online documentation browsing system. This page (the Directory node) gives a menu of major topics. button2 on a highlighted word follows that cross-reference. button3 anywhere brings up a menu of commands. ? lists additional keyboard commands. h invokes the Info tutorial. * Menu: XEmacs 21.5 =========== * XEmacs: (xemacs). XEmacs Editor. * Lispref: (lispref). XEmacs Lisp Reference Manual. * Intro: (new-users-guide). Introduction to the XEmacs Editor. * FAQ: (xemacs-faq). XEmacs FAQ. * Info: (info). Documentation browsing system. * Internals: (internals). XEmacs Internals Manual. Other Documentation: * Common Lisp: (cl). XEmacs Common Lisp emulation package. * Customizations: (custom). Customization Library. * Emodules: (emodules). XEmacs dynamically loadable module support. * External Widget: (external-widget). External Client Widget. * Standards: (standards). GNU coding standards. * Term mode: (term). XEmacs Terminal Emulator Mode. * Termcap: (termcap). Termcap library of the GNU system. * Texinfo: (texinfo). The GNU documentation format. * Widgets: (widget). The Emacs Widget Library.