Closed jlguenego closed 3 years ago
I think this constraint is an historic leftover which could be removed (PRs welcome π ).
However the limitation is on a token's name, not what the token pattern matches.
So there is nothing stopping you from creating a ENCODING_CONTROL
token which consumes "ENCODING-CONTROL" string
understood. So this is not a critical bug . Nonetheless I am going to do this PR ... for fun π
That would be most welcome π
I tried to do it ;)
Just for info, I just released a website that shows ASN.1 language stuff. This website is using chevrotain behinds. https://asn1.netlify.app/
Thanks again for this.
Now I finally know what ASN.1 is:
I will hopefully release a new Version of Chevrotain with the fix later this week. I will keep the issue open until then.
released in 7.1.0
First of all, thanks for this great lib.
I have this error during the
performSelfAnalysis
check.In the ASN1 language, there are some keyword that contains a dash character (-) like for instance :
Is there a reason for this control ? What is the recommanded way to proceed with this kind of keyword?
You can see my library that is using chevrotain here: https://github.com/jlguenego/asn.1