AleoHQ/leo
1
1
Fork 0
mirror of https://github.com/AleoHQ/leo.git synced 2024-12-20 08:01:42 +03:00
Code Issues Packages Projects Releases Wiki Activity

[ABNF] regenerate README.md

Browse Source
This commit is contained in:
Eric McCarthy 2022-03-14 12:35:56 -07:00
parent ffa8200d92
commit 572d59d67f
1 changed files with 25 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

38
docs/grammar/README.md
View File

@ -335,15 +335,26 @@ unary-expression = postfix-expression
In order to allow the recursion of the rule to stop, and
we need to regard, in the grammar, a primary expression as a unary expression
(i.e. a primary expression is also a unary expression in the grammar;
but note that the opposite is not true).
However, this is just a grammatical artifact: ```
ontologically, a primary expression is not really a unary expression, postfix-expression = primary-expression
because a unary expression is one that consists of / postfix-expression "." natural
a unary operator and an operand sub-expression. / ...
These terminological exceptions should be easy to identify in the rules. ```
In order to allow the recursion of the rule to stop, we need to regard, in the
grammar, a postfix or primary expression as a unary expression (i.e. a postfix
or primary expression is also a unary expression in the grammar; but note that
the opposite is not true). However, this is just a grammatical artifact:
ontologically, a postfix or primary expression is not really a unary
expression, because a unary expression is one that consists of a unary
operator and an operand sub-expression. These terminological exceptions
should be easy to identify in the rules.
-------- --------
@ -1241,7 +1252,8 @@ Go to: _[circuit-construction](#user-content-circuit-construction)_;
After primary expressions, postfix expressions have highest precedence. After primary expressions, postfix expressions have highest precedence.
They apply to primary expressions, and recursively to postfix expressions. They can be primary expressions, and there are a few kinds of postfix
expressions that have postfix expression subcomponents.
There are postfix expressions to access parts of aggregate values. There are postfix expressions to access parts of aggregate values.
A tuple access selects a component by index (zero-based). A tuple access selects a component by index (zero-based).
@ -1258,7 +1270,7 @@ There are three kinds of function calls:
top-level function calls, top-level function calls,
instance (i.e. non-static) member function calls, and instance (i.e. non-static) member function calls, and
static member function calls. static member function calls.
What changes is the start, but they all end in an argument list. They start differently, but they all end in an argument list.
Accesses to static constants are also postfix expressions. Accesses to static constants are also postfix expressions.
They consist of a named type followed by the constant name, They consist of a named type followed by the constant name,
@ -1355,8 +1367,8 @@ ordering-expression = additive-expression
Go to: _[additive-expression](#user-content-additive-expression)_; Go to: _[additive-expression](#user-content-additive-expression)_;
Equalities return booleans but may also operate on booleans; Next in the precedence order are equivalence relations.
the rule below makes them left-associative. These are not associative, since `a == b == c` could be confusing.
<a name="equality-expression"></a> <a name="equality-expression"></a>
```abnf ```abnf