Hi,
I was testing your lib and faced with exception: Non-terminating decimal expansion; no exact representable decimal result.

I was trying to do the following:

BigDecimal bigDecimal = BigDecimal.Parse("45465464646546546464646446547777777777777777777777777777888888888888888888888888888888777777777778542222222222221333333335");
         bigDecimal /= 700;
         MessageBox.Show(bigDecimal);

I expect thta it must return decimal result as a string, but it throws an exception instead.

Could this be fixed?

Similar to issue #6 the > and < operators of BigDecimal are swapped.

Extend the supported profiles for the PCL model

Assert.AreEqual(16, 
               BigDecimal.Parse("9999,9999,9999,9999".Replace(",", ""))
                           .StripTrailingZeros().Precision);

It fails, with the actual value being 17 ... Yikes! Something to do with StripTrailingZeros ...

I've also seen issues with unnecessary rounding, when Parsing strings with a MathContext with a precision of 16, and where there's only been 16 digits. Probably negative numbers, cause I've seen negative numbers created using a big integer constructor, with a Precision of 17 when there's clearly only 16 digits, and that when you Abs() the value the Precision is 16.

I'm using <package id="dmath" version="1.5.66" targetFramework="net45" />

I feel like this package needs a lot more testing? I don't really have the time at the moment.

Develop and deploy a version of Deveel Math library for the Portable Class Library profile (for mobile systems)

Hi,
Biginteger > < operators are returning the opposite
https://github.com/deveel/deveel-math/blob/master/src/Deveel.Math/Deveel.Math/BigInteger.cs#L1765

should be: return a.CompareTo(b) > 0;

Hi. Found another issue.

The following code:

BigDecimal bigDecimal = new BigDecimal(1000);
bigDecimal += 0.0005;

Will give result 1000.1, which is not what I expect.
Could this be workaround somehow or maybe I am missing something?

And another issue:

BigDecimal bigDecimal = new BigDecimal(1000.0005);

Will give me

Why not 1000.0005 exactly?

I tried to calculate this:
BigDecimal.Parse("-3.8272") / BigDecimal.Parse("-4.448")
which resulted to the following exception.
Non-terminating decimal expansion; no exact representable decimal result.

Is there no support for this type of calculation, I mean dividing two negative rational numbers?

Thx

UPDATE:
I figured it out. However I am not really satisfied with it.
The / operator does not use a context with a precision and rounding method, so the explicit Divide method should be used. Which is however not trivial without any kind of documentation. And could be addressed by using a default context with a standard precision. Because in this case the / operator is really just misleading, since the program can throw exceptions at random places.