Yeah, but the problem isn’t on ‘nix, it’s on Windows and specifically in
PowerShell.
Regards,
John Ralls
Although I have never looked at this shell language before, I suspect
"complete". Going to the formal language definition, it clearly makes
provision for conversion of numbers expressed as strings into numeric value:
6.16 Conversion from string to numeric type
Depending on its contents, a string can be converted explicitly or
implicitly to a numeric value. Specifically,
* An empty string is converted to the value zero.
* Leading and trailing spaces are ignored; however, a string may not
consist of spaces only.
* A string containing only white space and/or line terminators is
converted to the value zero.
* One leading + or - sign is permitted.
* An integer number may have a hexadecimal prefix (0x or 0X).
* An optionally signed exponent is permitted.
* Type suffixes and multipliers are not permitted.
* The case-distinct strings "-Infinity", "Infinity", and "NaN" are
recognized as the values -∞, +∞, and NaN, respectively.
You can see how little time it took me to find this. (first find the
formal definition of the language, then this section)
Michael D Novack
--
_______________________________________________
gnucash-user mailing list
gnucash-user@gnucash.org
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.
