Jörg Singer

Can be solved by an extra application as proposed in my last comment. To parse parol syntax create a bin crate with ``` parol new ... ``` and use parol's...

@jgoppert , Thank you for your friendly feedback. I'm always grateful for new ideas and for reports of difficulties which show up in real world projects. Parol’s great idea is...

## 1. Provision of member names For the first suggestion, the member names provision, I could imagine the following change in `parol`'s grammar description: Before: ```ebnf ASTControl : CutOperator |...

I like the `%production_type` approach. This is also in line with the `%user_type` directive. During my writing above I had a similar thought like ```ebnf ... %% class_definition %is Class;...

These are good news. 💯 I'd like to know what k (i.e. the k in LL(k)) the resulting grammar has. You can find it as constant MAX_K in the parser...

k=2 should not be a big problem. So, I would not make much effort to optimize this anymore.

I have a very first version of topic 1 on the branch [ast_member_names](https://github.com/jsinger67/parol/tree/ast_member_names) available. It also includes a modified VSCode extension and a language server. Tomorrow I'll do some honing...

Now the first feature "User defined member names / Grammar labeling" is complete on the above mentioned branch. I had to bump parol to version 3.0.0 because a few public...

This would be helpful. But, please take the time you need. There's no need to hurry. I'll be working on the second topic in the meantime in my spare time....

Both features are available on branch [nt_types](https://github.com/jsinger67/parol/tree/nt_types). I will do some tests and polishing on this branch before merging it to main. In summary this was easier than anticipated. Fortunately...