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
The JSon parser is define by six rules dedicated to `number`, `string`, `null`, `boolean`, `array`
99
+
The JSon parser is define by six rules dedicated to `number`, `string`, `null`, `boolean`, `array`
95
100
and `object`.
96
101
97
102
#### JSON Rules
@@ -123,9 +128,11 @@ parsec_rules!(
123
128
124
129
## The expression parser thanks to pipelined parsers.
125
130
126
-
The previous parser mixes char analysis and high-level term construction. This can be done in a different manner since Celma is a generalized parser combinator implementation.
131
+
The previous parser mixes char analysis and high-level term construction. This can be done in a different manner since
132
+
Celma is a generalized parser combinator implementation.
127
133
128
-
For instance a first parser dedicated to lexeme recognition can be designed. Then on top of this lexer an expression parser can be easily designed.
134
+
For instance a first parser dedicated to lexeme recognition can be designed. Then on top of this lexer an expression
135
+
parser can be easily designed.
129
136
130
137
### Tokenizer
131
138
@@ -142,7 +149,7 @@ parsec_rules!(
142
149
143
150
### Lexemes
144
151
145
-
The Lexeme parser recognizes simple token keywords.
152
+
The Lexeme parser recognizes simple token keywords.
146
153
147
154
```rust
148
155
parsec_rules!(
@@ -155,8 +162,10 @@ parsec_rules!(
155
162
156
163
### Expression parser
157
164
158
-
The expression parser builds expression consuming tokens. For this purpose the stream type can be specified for each parser. If it's not the case the default one is `char`.
159
-
In the following example the declaration `expr{Token}:{Expr}` denotes a parser consuming a `Token` stream and producing an `Expr`.
165
+
The expression parser builds expression consuming tokens. For this purpose the stream type can be specified for each
166
+
parser. If it's not the case the default one is `char`.
167
+
In the following example the declaration `expr{Token}:{Expr}` denotes a parser consuming a `Token` stream and producing
0 commit comments