Definition of <bit string literal> not found.

[GCer-Hidenori]

At line 220 of sql-2003-2.bnf,<bit string literal> is used.
But there is no definition.

[ronsavage]

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].

Links: ------ [1] #24 [2] https://github.com/notifications/unsubscribe-auth/AAAFH6AWWTSNEAUNPW2X6WDRHQ7W5ANCNFSM4LKI6TIA

[GCer-Hidenori]

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]

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].

Links: ------ [1] #24 (comment) [2] https://github.com/notifications/unsubscribe-auth/AAAFH6BN4LGYADKSQQ5XBPDRHS7DZANCNFSM4LKI6TIA

[GCer-Hidenori]

Hi

Yes,you are right.
<token> is defined at line 213

But there is no reference to it from anywhere.

[ronsavage]

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].

Links: ------ [1] #24 (comment) [2] https://github.com/notifications/unsubscribe-auth/AAAFH6BMPCRUS55I3FY26O3RI37PZANCNFSM4LKI6TIA

[GCer-Hidenori]

I’m very happy to hear your operation was successful.
I hope you could leave the hospital soon.

[ronsavage]

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].

Links: ------ [1] #24 (comment) [2] https://github.com/notifications/unsubscribe-auth/AAAFH6EBXVMQM6CEQKYW4O3RJWUVVANCNFSM4LKI6TIA

[GCer-Hidenori]

There are times like that.
Have a good rest.

[Schultzer]

<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]

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:

1. https://en.wikipedia.org/wiki/Extended_Backus%E2%80%93Naur_form
2. https://tomassetti.me/ebnf/

Lastly note that we are now using sql-2016.ebnf.

[ronsavage]

As I feared. After I click the green Comment button in github, it echos my text with '<token>' reduced to ''.

[ronsavage]

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]

Found another typo:
you would use to create each token
should read:
you would use it to create each token