Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Docs: Clarify BNF description in "introduction.rst" #14492

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

Closed
wants to merge 2 commits into from
Closed

Docs: Clarify BNF description in "introduction.rst" #14492

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
781418f
BNF description fix
aeros Jul 1, 2019
ec90e53
Added suggestion from taleinat
aeros Jul 1, 2019
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
Prev Previous commit
Added suggestion from taleinat 
Improve the clarity by changing ``or`` to ``and/or``. This simultaneously satisfies the logical operation and English contexts.
  • Loading branch information
@aeros
aeros authored Jul 1, 2019
commit ec90e5354fc840cc94991af38a2bf91a5d5458df
2 changes: 1 addition & 1 deletion Doc/reference/introduction.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -98,7 +98,7 @@ notation. This uses the following style of definition:
lc_letter: "a"..."z"

The first line says that a ``name`` is an ``lc_letter`` followed by a sequence
of zero or more ``lc_letter``\ s or underscores. An ``lc_letter`` in turn is
of zero or more ``lc_letter``\ s and/or underscores. An ``lc_letter`` in turn is
any of the single characters ``'a'`` through ``'z'``. (This rule is actually
adhered to for the names defined in lexical and grammar rules in this document.)

Expand Down