Generalize parse() to run() and match() to eval() #28

xparq · 2023-09-06T20:27:16Z

run() has been added now, but it's really just a purely syntactic reminder:
- for it to really be useful, the usual concepts related to running process -- input, output, error management etc. -- i.e. a runtime context must also be developed.
match(), as eval(), similarly, should then also use the runtime context struct instead of all the parsing-related (in/out) parameters directly

Nested structures like { some = code; { block; {another} stuff} yay } can be parsed now recursively. + Rule tree: name lookup for _USE (no generic find() yet) + #14: Recursion is implemented, but not via _SELF yet + #15 (_DEF/_USE) + #28: Parser::run() added + OPERATORS -> CONST_OPERATORS, preparing to taking it seriously (RULE.name is mutable though, for _DEF to still work on const rules, but that's a tmp. kludge!) + Fix #29: Crash in _DEF for missing len = 0 + Better diagnostics (tests, debug messages etc.) + Comments, cosmetics

Nested structures like { some = code; { block; {another} stuff} yay } can be parsed now with (almost) the ususal recursive grammar productions. + Rule tree: name lookup for _USE (no generic find() yet) + #14: Recursion is implemented, but not via _SELF yet + #15 (_DEF/_USE) + #28: Parser::run() added + OPERATORS -> CONST_OPERATORS, preparing to taking it seriously (RULE.name is mutable though, for _DEF to still work on const rules, but that's a tmp. kludge!) + Fix #29: Crash in _DEF for missing len = 0 + Better diagnostics (tests, debug messages etc.) + Comments, cosmetics

xparq mentioned this issue Sep 7, 2023

Grammar preprocessing/compilation phase (after construction, before parsing) #31

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Generalize parse() to run() and match() to eval() #28

Generalize parse() to run() and match() to eval() #28

xparq commented Sep 6, 2023 •

edited

Generalize parse() to run() and match() to eval() #28

Generalize parse() to run() and match() to eval() #28

Comments

xparq commented Sep 6, 2023 • edited

xparq commented Sep 6, 2023 •

edited