I was showing off Take Command to a friend (I’m somewhat of an evangelizer for Take Command (with little success so far, sadly)) and I was demonstrating Take Command’s high-precision arithmetic and sadly ran into that inconsistency with maximum (environment) variable and possibly command-line length (a little less than 4K on my system as far as I can tell) and @Eval’s maximum precision (1 place for sign plus 10,000 digits to the left of the decimal point plus the decimal point plus 10,000 digits after the decimal point yields 20002 characters – almost 5 times larger than what an environment variable can contain). @Eval’s maximum precision is almost meaningless given these “external” limitations – and, after a lot of experimentation (like writing the result to a file and trying to read that file) came to nothing. I don’t quite know what my suggested solution would be – making the maximum length of an environment variable/command line 20K characters seems to be a little excessive – maybe the best solution is something to do with @ExecStr – although I don’t really know what the “command” would be….