axilmar

I am about to complete the new version. I've also added debug annotations, as we said earlier. Do you have any other particular feature that you want to see in...

I have lots of small examples in the new documentation, but I may do some more extensive ones.

It's impossible to find out which rule is the problematic one. I suggest to add a name field in a rule, then set up their name, and then when it...

Add the following field to the rule class: const char* name; Then set the names of your rules: my_rule1.name = "my rule1"; Then when the crash happens, you can see...

Nice that you found it. While writing and documenting an example which uses the library, I added some new features that will help debugging a lot. The new feature is...

I actually uploaded the new version because my computer almost crashed today, and I was afraid I will lose it. I've changed a few things, sorry for the inconvenience, but...

Indeed. It was not the best approach. Now you have to write parse_context I have written a very detailed explanation of the parse context in the readme (which I should...

Why do I have a setter for the name there? I will remove the setter. The parse nodes are supposed to be immutable, except for the rule class. Στις Τετ...

You can always use your custom source type. For example: using my_parse_context = parserlib::parse_context; The method 'derive_parse_context' is used as a helper method that allows using the matches produced by...

Indeed, it's correct, if you want to use the matches created by the lexer as input to the parser. Στις Πέμ 27 Νοε 2025 στις 4:46 π.μ., ο/η ollydbg ***@***.***>...