Mercurial > hg > xemacs-beta

comparison man/lispref/numbers.texi @ 2033:a7b2d995287f

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
[xemacs-hg @ 2004-04-19 11:25:58 by stephent] document featurep features <873c70us4l.fsf@tleepslib.sk.tsukuba.ac.jp>
author stephent
date Mon, 19 Apr 2004 11:26:04 +0000
parents cc89c76c4b17
children e52c5a5c6a7d
comparison
equal deleted inserted replaced
2032:cc89c76c4b17 2033:a7b2d995287f
319 implementation provides arbitrary precision integers, but ratios were 319 implementation provides arbitrary precision integers, but ratios were
320 implemented by the XEmacs implementer, Jerry James, who is not a 320 implemented by the XEmacs implementer, Jerry James, who is not a
321 numerical analyst. Arbitrary precision floats are not available with 321 numerical analyst. Arbitrary precision floats are not available with
322 MP. 322 MP.
323 323
324 If your code needs to run correctly whether or not the feature is
325 provided, you may test for the features @code{bignum}, @code{ratio}, and
326 @code{bigfloat}.
327
324 The XEmacs bignum facility implements the Common Lisp notion of 328 The XEmacs bignum facility implements the Common Lisp notion of
325 @dfn{contagion}, so that integers are always represented using the 329 @dfn{contagion}, so that integers are always represented using the
326 ``smallest'' representation that is exact, and integral ratios are 330 ``smallest'' representation that is exact, and integral ratios are
327 converted to integers. Since floating point arithmetic is inherently 331 converted to integers. Since floating point arithmetic is inherently
328 imprecise, numbers are implicitly coerced to bigfloats only if other 332 imprecise, numbers are implicitly coerced to bigfloats only if other