evalexpr/src/parse
Bruno BELANYI 32d17134cd evalexpr: parse: parse operand more correctly
I noted that the `right_prec` and `next_prec` functions taking a
character only work because prefix operators come after infix operators
in the table. We should compare the *actual* operator kind, which would
probably need a single operator enum to make sure there are no
collisions.
2020-11-02 15:48:30 +01:00
..
climbing_parse.c evalexpr: parse: parse operand more correctly 2020-11-02 15:48:30 +01:00
operators.inc evalexpr: parse: add precedence climbing parser 2020-11-02 15:48:29 +01:00
parse.h evalexpr: parse: add precedence climbing parser 2020-11-02 15:48:29 +01:00
recursive_parse.c evalexpr: parse: rename recursive parsing function 2020-11-02 15:48:29 +01:00