Am I going crazy or is Math.Pow broken?

Question

I used the base converter from here and changed it to work with ulong values, but when converting large numbers, specifically numbers higher than 16677181699666568 it was returning incorrect values. I started looking into this and discovered that Math.Pow(3, 34) returns the value 16677181699666568, when actually 3^34 is 16677181699666569. This therefore throws a spanner in the works for me. I assume this is just an issue with double precision within the Pow method? Is my easiest fix just to create my own Pow that takes ulong values?

If so, what's the quickest way to do Pow? I assume there's something faster than a for loop with multiplication each time.

Thanks all... BigInteger.Pow works beautifully. – Will Calderwood Mar 23 '11 at 16:53 — Will Calderwood, Mar 23 '11 at 16:53

score 7 · Accepted Answer · edited May 23 '17 at 11:55

7

You can use BigInteger.Pow. Or use my power method for long.

edited May 23 '17 at 11:55

Community

1
1

answered Mar 23 '11 at 15:08

Yuriy Faktorovich

67,283
14
105
142

score 6 · Answer 2 · answered Mar 23 '11 at 15:09

The problem is that Math.Pow returns a double, and the closest double value to 16677181699666569 is 16677181699666568.

So without getting Math.Pow involved:

long accurate = 16677181699666569;
double closestDouble = accurate;
// See http://pobox.com/~skeet/csharp/DoubleConverter.cs
Console.WriteLine(DoubleConverter.ToExactString(closestDouble));

That prints 16677181699666568.

In other words whatever Math.Pow does internally, it can't return a result that's more accurate than the one you're getting.

As others have said, BigInteger.Pow is your friend if you're using .NET 4.

Richard · Answer 3 · 2016-10-30T21:46:25.720

5

Read What Every Computer Scientist Should Know About Floating-Point

Floating point types are an approximation, the rounding you see is normal.

If you want exact results use BigInteger.

edited Oct 30 '16 at 21:46

answered Mar 23 '11 at 15:08

Richard

106,783
21
203
265

score 1 · Answer 4 · answered Mar 23 '11 at 15:10

1

I assume this is just an issue with double precision within the Pow method?

Yes.

Is my easiest fix just to create my own Pow that takes ulong values?

You can use BigInteger.Pow.

answered Mar 23 '11 at 15:10

ysth

96,171
6
121
214

score 0 · Answer 5 · answered Mar 23 '11 at 15:09

If you're using .NET Framework 4, Microsoft has included a new BigInteger class that lets you manipulate large numbers.

http://msdn.microsoft.com/en-us/library/system.numerics.biginteger.aspx

Alternatively, you can use a nice library that someone else created:

http://intx.codeplex.com/ (IntX library)

Am I going crazy or is Math.Pow broken?

5 Answers5

Linked