>
> I wonder what's the reason to support such old
> sbcl? To support hardware other than x86?
Well, it is not my job to tell people which version
of software they should use. There are good reasons
to run 10 years old binaries. And reversing
question: why not? To the moment support for
older
oldk1331 wrote:
>
> My point is, base 2 and IEEE format can make sure
> DFLOAT in FriCAS is hardware accelerated, like
> MachineInteger, U32Vector, etc.
But DFLOAT is hardware accelerated _now_. We use whatever
underlying Lisp offers us and all supported Lisps
use machine arithmetic to perform
I wonder what's the reason to support such old
sbcl? To support hardware other than x86?
--
You received this message because you are subscribed to the Google Groups
"FriCAS - computer algebra system" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
My point is, base 2 and IEEE format can make sure
DFLOAT in FriCAS is hardware accelerated, like
MachineInteger, U32Vector, etc.
--
You received this message because you are subscribed to the Google Groups
"FriCAS - computer algebra system" group.
To unsubscribe from this group and stop
oldk1331 wrote:
>
> Just checked, sbcl, clisp, gcl, ecl all return 2 for float-radix.
> Maybe we should check float-radix and :IEEE-FLOATING-POINT
> in *FEATURES* in configure script.
What would we gain from such a check? BTW: IEEE mandates
x ~= x when x is a NaN. We definitely do not want
oldk1331 wrote:
> I found that documentation for "precision()" is vague:
>
> In sf.spad:
>precision : () -> PositiveInteger
> ++ precision() returns the precision in digits base.
>
> precision : PositiveInteger -> PositiveInteger
> ++ precision(n) set the precision in the
oldk1331 wrote:
>
> Backported from openaxiom.
>
> 1. Ring already has Monoid
>
> 2. OrderedRing already has abs
>
> 3. sb-ext:quit is deprecated for a long time
The first two are obvious. But the third one is a bit
more complicated. Namely, currently we claim that
FriCAS can be build using
>
> > For exact exponsnts it should give 1.
>
> One more fix for ^(DFLOAT, FRAC INT) :
>
> diff --git a/src/algebra/sf.spad b/src/algebra/sf.spad
> index 28af4bb..b7e5cf3 100644
> --- a/src/algebra/sf.spad
> +++ b/src/algebra/sf.spad
> @@ -613,7 +613,7 @@
>
> x : % ^ r : Fraction Integer
> For exact exponsnts it should give 1.
One more fix for ^(DFLOAT, FRAC INT) :
diff --git a/src/algebra/sf.spad b/src/algebra/sf.spad
index 28af4bb..b7e5cf3 100644
--- a/src/algebra/sf.spad
+++ b/src/algebra/sf.spad
@@ -613,7 +613,7 @@
x : % ^ r : Fraction Integer ==
zero? x =>
-
Backported from openaxiom.
1. Ring already has Monoid
2. OrderedRing already has abs
3. sb-ext:quit is deprecated for a long time
diff --git a/src/algebra/catdef.spad b/src/algebra/catdef.spad
index 5a7b371..ce919f6 100644
--- a/src/algebra/catdef.spad
+++ b/src/algebra/catdef.spad
@@ -1061,7
>
> What's the right thing to do?
>
> (1) -> 0.0 ^ (0::NNI)
>
>(1) 1.0
> Type: Float
> (2) -> 0.0 ^ (0::INT)
>
>>> Error detected within library code:
>0^0 is undefined
For exact exponsnts it should give 1.
> (4)
They are all correct except (0.0::DFLOAT) ^ (0::INT), aren't they?
--
You received this message because you are subscribed to the Google Groups
"FriCAS - computer algebra system" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
What's the right thing to do?
(1) -> 0.0 ^ (0::NNI)
(1) 1.0
Type: Float
(2) -> 0.0 ^ (0::INT)
>> Error detected within library code:
0^0 is undefined
(2) -> (0.0::DFLOAT) ^ (0::INT)
(2) 1.0
13 matches
Mail list logo
