Skip to content

docs: fix inaccurate non-terminal naming rules in GBNF README #26489

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.

Sign up for GitHub

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

Open
JingliangGao wants to merge 1 commit into
base: master
Choose a base branch
from
+1 −1
Open

docs: fix inaccurate non-terminal naming rules in GBNF README #26489

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion grammars/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,7 @@ castle ::= ...

## Non-Terminals and Terminals

Non-terminal symbols (rule names) stand for a pattern of terminals and other non-terminals. They are required to be a dashed lowercase word, like `move`, `castle`, or `check-mate`.
Non-terminal symbols (rule names) stand for a pattern of terminals and other non-terminals. They may contain letters, digits, hyphens, and underscores, and typically start with a lowercase letter — though camelCase names are also valid (e.g. `dataType`, `relationOperator`). Examples: `move`, `castle`, `check-mate`, `dataType`.

Terminals are actual characters ([code points](https://en.wikipedia.org/wiki/Code_point)). They can be specified as a sequence like `"1"` or `"O-O"` or as ranges like `[1-9]` or `[NBKQR]`.

Expand Down