Closed dkahle closed 5 years ago
Well, I see the issue. Macaulay2 is inconsistent with its toExternalString format for floating points. For example,
> m2("1+1.1")
[1] ".21000000000000001p53e1"
> m2_parse(m2("1+1.1"))
[1] 2.1
is parsed correctly, whereas the output above returned from M2 by gb()
contains "1.1", a different format for floating point values than the parser was expecting.
> m2_parse("{1.1}")
# ERROR
> m2("{1.1}")
[1] "{.11000000000000001p53e1}"
> m2_parse(m2("{1.1}"))
M2 List
[[1]]
[1] 1.1
Hm, tests don't pick up any problems, but I worry about downstream parsing errors with that kind of thing. Is there any Macaulay2 documentation of that behavior?
Guillaume Pouliot brought this to my attention; looks like a parser error. Thoughts?
Created on 2019-08-11 by the reprex package (v0.2.1)