Above you see precision building for the first 20 iterations until decimal place truncation automatically occurs. Instead of the arbitrary truncation of 30, it had ought to start at 50 positions to allow for maximal precision. No?
$pi contains 50 decimal places, as requested by maroon, to allow for enough precision for the default maximum of 30 decimal places that mIRC returns for bigfloat calculations. If I extend the maximum returned by calculations to 50 decimal places, I would need to extend $pi to 70 decimal places. And so on.
NASA uses
15 digits of PI for most calculations. At most 37 digits of PI are needed to relate the size of the known universe to that of a hydrogen atom.
30 decimal places seems to be a reasonable limit for most uses.
What calculation are you performing that would require 200 decimal places? :-]
That said, I am a little disappointed that %pt.bf $calc(0.0000000000000000000000000000000000000000000054) is returning 0 seconds for Planck Time. I mean, how am I going to determine my dog's next feeding time with that kind of inaccuracy?
I'll be adding a /bigfloat -dN switch to my to-do list to allow you to set the required number of decimal places. I am still working on stabilizing bigfloat support, so this may not be added just yet.
However, note that increasing the number of significant digits/decimal places that the MAPM library uses/returns decreases calculation speed significantly, so it is not something you should do unless you need it.
