Administrator

I am impressed that the author was able to beat CMD into producing these results. And saddened that he wasted days of his life doing it.

The same result of his 195-line CMD batch file can be done in 1 line in TCC:

echo pi = %@eval[pi=0.108]

Or if you want a really high resolution pi:

echo pi=%@eval[pi=0.10000]

TCC calculating pi to 10,000 decimal places runs about 600 times faster than the CMD batch file calculating it to 108 places.

And the reason the batch file doesn't run in TCC is because of invalid syntax in his SET /A statements. Which CMD is rewriting internally to the correct format, which is (1) undocumented, and (2) inconsistent with how it parses SET statements without the /A. But I have made a change for 21.01.50 to emulate this undocumented behavior. Who knows, it might even be a CMD "feature".