Changes
http://page.axiom-developer.org/zope/mathaction/167InfiniteFloatsDomain/diff
--
++added:
>From William Sit, Tuesday June 14 20:06:00 -4:00
Subject: Float, Real, RealClosure
Tim wrote:
>This raises the same kind of implementation issue that indefinite computation
>raises except that i
Changes
http://page.axiom-developer.org/zope/mathaction/167InfiniteFloatsDomain/diff
--
??changed:
-$m$ has 53 bits stored in a 52 bit field (not including sign, note that in
base 2, the most significant digit normalized must be 1, so no need to store
it!) and $e$ has 11 bits (including sign, r
Changes
http://page.axiom-developer.org/zope/mathaction/167InfiniteFloatsDomain/diff
--
??changed:
-In 'FLOAT', conceptually the infinite precision floating point system, is
basically also finite precision floating point system, with the ability to
increase precision as requested. However, this
Changes
http://page.axiom-developer.org/zope/mathaction/167InfiniteFloatsDomain/diff
--
??changed:
-What is the domain FLOAT if not already "infinite but bounded
What is the domain 'FLOAT' if not already "infinite but bounded
++added:
++added:
>From Tim Daly Sun, 12 Jun 2005 17:17:54 -0500
Changes
http://page.axiom-developer.org/zope/mathaction/167InfiniteFloatsDomain/diff
--
Tim,
What is the domain FLOAT if not already "infinite but bounded
length"? I thought that FLOAT has internal representation based
on a pair of "infinite but bounder length" INT's.
>From 'float.spad.pamphlet'
