You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
add more tests to cover current system even for more complex expression (bugfix v1.x if there's still some bug)
write tests for C++ precedence expression evaluator
implement the new precedence, probably just patch the current code
consider full refactoring to avoid the recursive approach, but research first what can be gain by avoiding the recursive evaluator, feels like the performance is suffering from it, but without benchmarking and research this is bogus claim.
string literals: reconsider to have the same escaping as C++, that means also in single apostrophes, maybe even support for full C++ escaping rules (maybe even those unfortunate octals? But only in strings?)
reconsider having octals as C++ ... (I mean no, just no, it's horrible) (but let's consider it one more time for v2.x)
help wanted: to add tests for more tricky expressions and exercising current precedence, to verify v1.x correctness
The text was updated successfully, but these errors were encountered:
ped7g
changed the title
Change operator precedence to C++ standard.
Change operator precedence to C++ standard, string literals escaping too
Aug 11, 2019
help wanted: to add tests for more tricky expressions and exercising current precedence, to verify v1.x correctness
The text was updated successfully, but these errors were encountered: