decimal

In my program, decimal accuracy is very important. A lot of my calculations must be accurate to many decimal places (such as 50). Because I am using python, I have been using the decimal module (with context().prec = 99. ie; Set to have 99 decimal places of accuracy when instantiating a decimal object ) as pythonic floats don't allow anywhere near such accuracy. Since I wish for the User to specify the decimal places of accuracy of the calculations, I've had to implement several round() functions in my code. Unfortuneately, the inbuilt round function and the decimal object do not interact well

Simple question - why does the Decimal type define these constants? Why bother? I'm looking for a reason why this is defined by the language, not possible uses or effects on the compiler. Why put this in there in the first place? The compiler can just as easily in-line 0m as it could Decimal.Zero, so I'm not buying it as a compiler shortcut. JaredPar Small clarification. They are actually static readonly values and not constants. That has a distinct difference in .Net because constant values are inlined by the various compilers and hence it's impossible to track their usage in a compiled

I have a variable of decimal type and I want to check the number of digits before decimal point in it. What should I do? For example, 467.45 should return 3 . Solution without converting to string (which can be dangerous in case of exotic cultures): static int GetNumberOfDigits(decimal d) { decimal abs = Math.Abs(d); return abs < 1 ? 0 : (int)(Math.Log10(decimal.ToDouble(abs)) + 1); } Note, that this solution is valid for all decimal values UPDATE In fact this solution does not work with some big values, for example: 999999999999998 , 999999999999999 , 9999999999999939 ... Obviously, the