Re^2: floating point addition

It says that it is “implemented mostly in XS,” but I have not taken the time to see whether it uses microprocessor decimal-math

I don't think it does, but it certainly does decimal (as opposed to binary) arithmetic - and should be more than adequate for most people wanting to perform base 10 arithmetic.

OTOH, my Math::Decimal64 and Math::Decimal128 modules do make use of the _Decimal64 and _Decimal128 types, and associated operations:

C:\>perl -MMath::Decimal64 -le "$x=Math::Decimal64->new(0); $x += Math
+::Decimal64->new('20.1') for (1..43);print $x;"
8643e-1
[download]

The user interface is a little awkward, mainly because gcc does not provide strtod64 or strtod128 functions, and does not provide any (s)printf formatters for the _Decimal64 and _Decimal128 type.

I'm working on improving that interface - and the current git version provides for output in floating point format instead of just scientific notation (ie as 864.3 instead of 8643e-1 for the quoted example).
I must also add overloading of strings - so that the above one liner can be rewritten as:

perl -MMath::Decimal64 -le "$x=Math::Decimal64->new(0); $x += '20.1' f
+or (1..43);print $x;"
[download]

But I don't want to add overloading of NVs as that would defeat the purpose.

(That takes care of this month's quota of self-promotion ;-)

Cheers,
Rob

Comment on Re^2: floating point addition Select or Download Code

Replies are listed 'Best First'.
Re^3: floating point addition by RonW (Parson) on Jan 13, 2015 at 00:15 UTC
But I don't want to add overloading of NVs as that would defeat the purpose. How would this defeat the purpose?	[reply]
Re^4: floating point addition by syphilis (Archbishop) on Jan 13, 2015 at 01:52 UTC
Because allowing use of NV values re-introduces the very rounding anomalies we're (normally) trying to avoid: `C:\>perl -MMath::Decimal64=":all" -le "$x=Math::Decimal64->new('0.085' +); $y = Math::Decimal64->new(0.085);$z = NVtoD64(0.085);print $x;prin +t $y; print $z;" Outputs: 85e-3 8500000000000001e-17 8500000000000001e-17` [download] $y and $z are assigned from the actual NV value, whereas $x is assigned the specified decimal value. The trouble with allowing overloading of NVs is that it makes it just too easy for people to inadvertently use a value that they didn't really mean to use - though I guess the same criticism could be levelled at new() because it currently allows assignment of NVs. NVtoD64() ought to be there so that one can assign the NV to a Math::Decimal64 object if one wants. It's name pretty much explicitly indicates what it's going to do, thus making it less likely that one will inadvertently assign an unintended value. Cheers, Rob	[reply] [d/l]