v0.1.12
BinaryOperatorRegistry
no longer ends up in an invalid state when anInvalidArgumentException
thrown byBinaryOperatorRegistry::register()
is handled- Numbers with multiple decimal points (such as
3..2
,3.2.1
, etc.) are no longer parsed as numeric literals - Function call token's "end pos" is now at closing parenthesis of its argument list
- Parse exceptions arising from function calls are more comprehensible
// before > tan(x) + tan(y) tan(z) ** tan(w) Unexpected Function Call token encountered at "tan" (16:19) in "tan(x) + tan(y) tan(z) ** tan(w)" // after > tan(x) + tan(y) tan(z) ** tan(w) Unexpected Function Call token encountered at "tan(z)" (16:22) in "tan(x) + tan(y) tan(z) ** tan(w)"
- Parse exceptions arising from function calls are more comprehensible