Open xor2003 opened 3 years ago
make_token
. Then, you can use the dict as actions
in Parser construction to attach your action to all rules. Yes, parglare is alive project. I'm using it actively and intend to maintain it for the foreseeable future. The development pace is slower at the moment as it has more or less all the features I need at the moment. Currently, with textX/Arpeggio and this project I don't plan to make another parsing framework for Python. Maybe in some other language :)magic to resolve recursions
?
Description
['token_value']
but( token_name, 'token_value' )
I wrote the action:
Example:
[('register', 'al'), ('INTEGER', '0')]]
But I want it to be a generic for all rules. I mean I don't want to define this action for all rules.
Since I want to do additional processing after parsing. Am I doing it wrong? Should all the processing done in the actions? I saw it will be actions with side effect added to parglare later. Do you see the parglare as alive project or you are going to develop something new?
As I understand parsing tree is similar to what I want. But it's structure is complex and if I enable building parse tree and call actions during the parsing the actions called in random order and sometimes twice. Probably twice is a bug, right?
Parglare is doing some magic to resolve recursions. Can it produce resulting human readable EBNF?