You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi
And at 221 <hex string literal> likewise. This is probably due to the
way Jonathan converted the html into bnf. Or some things in the standard
are defined in another standard. The latter is most likely.
---
Ron Savage
savage.net.au
On 2020-03-15 13:56, GCer-Hidenori wrote:
At line 220 of sql-2003-2.bnf,<bit string literal> is used.
But there is no definition.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub [1], or unsubscribe [2].
I found strange thing. <bit string literal> is used in <nondelimiter token> definition.
And <nondelimiter token> is used in <token> definition.
But <token> is used nowhere.
Hi
<token> is defined at line 213:
<token> ::= <nondelimiter token> | <delimiter token>
---
Ron Savage
savage.net.au
On 2020-03-15 22:57, GCer-Hidenori wrote:
I found strange thing.
<bit string literal> is used in <nondelimiter token> definition.
And <nondelimiter token> is used in <token> definition.
But <token> is used nowhere.
--
You are receiving this because you commented.
Reply to this email directly, view it on GitHub [1], or unsubscribe [2].
Hi
I'll have a look at it sometime, but I just got home from 6 days in
hospital, so I'm taking it easy right now. And the great news is that
the operation was 100% successful.
---
Ron Savage
savage.net.au
On 2020-03-23 17:36, GCer-Hidenori wrote:
Hi
Yes,you are right.
<token> is defined at line 213
But there is no reference to it from anywhere.
--
You are receiving this because you commented.
Reply to this email directly, view it on GitHub [1], or unsubscribe [2].
Hi
I'm home now, but very tired, so doing virtually no work.
---
Ron Savage
savage.net.au
On 2020-03-28 07:57, GCer-Hidenori wrote:
I'm very happy to hear your operation was successful.
I hope you could leave the hospital soon.
--
You are receiving this because you commented.
Reply to this email directly, view it on GitHub [1], or unsubscribe [2].
<token> is a root rule. If the rule is not defined any where then they are the root of the three. E.g when you build a lexer you would use <token> to create each tokens, then you can parse them into an AST and validate them based on the rest of the rules.
The email I received from Benjamin via github had a couple of references to '' missing. I will copy Benjamin's reply here just to see what happens. I suspect that string will vanish again:
is a root rule. If the rule is not defined anywhere else then it is the root of a tree. E.g when you build a lexer you would use to create each token, then you can parse them into an AST and validate them based on the rest of the rules.
So, one more try, using \<token to stop github gobbling up the <token> token!
<token> is a root rule. If the rule is not defined anywhere else then it is the root of a tree. E.g when you build a lexer you would use to create each token, then you can parse them into an AST and validate them based on the rest of the rules.
Activity
ronsavage commentedon Mar 15, 2020
GCer-Hidenori commentedon Mar 15, 2020
I found strange thing.
<bit string literal>is used in<nondelimiter token>definition.And
<nondelimiter token>is used in<token>definition.But
<token>is used nowhere.ronsavage commentedon Mar 16, 2020
GCer-Hidenori commentedon Mar 23, 2020
Hi
Yes,you are right.
<token>is defined at line 213But there is no reference to it from anywhere.
ronsavage commentedon Mar 25, 2020
GCer-Hidenori commentedon Mar 28, 2020
I’m very happy to hear your operation was successful.
I hope you could leave the hospital soon.
ronsavage commentedon Mar 28, 2020
GCer-Hidenori commentedon Mar 28, 2020
There are times like that.
Have a good rest.
Schultzer commentedon Jun 26, 2025
<token>is a root rule. If the rule is not defined any where then they are the root of the three. E.g when you build a lexer you would use<token>to create each tokens, then you can parse them into an AST and validate them based on the rest of the rules.ronsavage commentedon Jun 26, 2025
Hi GCer-Hidenori
The email I received from Benjamin via github had a couple of references to '' missing. I will copy Benjamin's reply here just to see what happens. I suspect that string will vanish again:
is a root rule. If the rule is not defined anywhere else then it is the root of a tree. E.g when you build a lexer you would use to create each token, then you can parse them into an AST and validate them based on the rest of the rules.
And here are some tutorials on ebnf:
Lastly note that we are now using sql-2016.ebnf.
ronsavage commentedon Jun 26, 2025
As I feared. After I click the green Comment button in github, it echos my text with '<token>' reduced to ''.
ronsavage commentedon Jun 26, 2025
So, one more try, using \<token to stop github gobbling up the <token> token!
<token> is a root rule. If the rule is not defined anywhere else then it is the root of a tree. E.g when you build a lexer you would use to create each token, then you can parse them into an AST and validate them based on the rest of the rules.
ronsavage commentedon Jun 26, 2025
Found another typo:
you would use to create each token
should read:
you would use it to create each token