-
Notifications
You must be signed in to change notification settings - Fork 150
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ID_Start and ID_Continue specification and regular expression #331
Comments
I believe it is the You can check this code for the model's definition of these constructs (derived from Unicode): openCypher/tools/grammar/src/main/java/org/opencypher/grammar/CharacterSet.java Lines 310 to 314 in 4a2896e
|
Will it be acceptable to change anything in the comments of the xml ? |
Sure, but please note that in order to accept contributions there is a CLA that must be signed. |
Ah ok, thank you for the notice. I won't sign anything so i won't make PR's here. If this isn't important for anyone else, this issue can be closed. Hopefully for other people they will be able to find this issue to get the information that is not (yet) in the xml .. |
I'll keep it open for a bit to see if someone (like me) decides to improve the comment, and will close at that point (or before if nothing happens). |
I'm looking at this
openCypher/grammar/basic-grammar.xml
Lines 718 to 740 in a514465
How should i implement this? When you look for unicode ID_Start there a jungle of documentation. But i only need the regex of this. Fortunately unicode has made a tool for this https://unicode.org/cldr/utility/regex.jsp?a=%5B%3AID_Start%3A%5D&b=
That leaves the question what about
And extended with a few characters
?So perhaps to clear up this section of the spec some of the following could be done:
I think the unicode tool gives the regular expression in some standard regex format, but there can be other engines like PCRE which can define other shorthand classes which could be used instead. Therefor it can be useful to include regular expressions in comments.
The text was updated successfully, but these errors were encountered: