Comments (3)
I think what you want is
rule string() -> NodeElement
= "\"" s:$([^'"']*) "\"" { string_node(s) }
/ "'" s:$([^'\'']*) "'" { string_node(s) }
- String literal expressions follow the same escaping as Rust string literals
- Inside of
[]
, you are writing a Rust pattern, just like in the arm of amatch
. It is matching on achar
for a parser overstr
, therefore you want a single quoted char pattern, which follows the same escaping as in Rust.
from rust-peg.
Hey, one more thing. I spent second night on it ;)
Here is updated version:
https://github.com/fazic/fazic_mono/blob/update_deps/src/fazic/parser.rs
vs rustpeg:
https://github.com/fazic/fazic_mono/blob/master/src/fazic/parser.rustpeg
They are not doing the same:
for example PRINT 2+2
not working :(
I think is something about expression()
rule. Rewrite from #infix.
Thanks in advance
from rust-peg.
In precedence!
, the @
or (@)
itself represents the recursive expression. It seems like the term()
calls don't belong next to it in each case, but instead as an atom case at the end. e.g.
rule expression() -> NodeElement = precedence! {
l:(@) _ ("AND" / "and") _ r:@ { node("and", vec![l, r]) }
// ... skipped ...
l:@ _ "^" _ r:(@) { node("pow", vec![l, r]) }
--
t:term() { t }
}
You could also call float
, integer
, string
etc directly at the bottom there as atom cases if you don't need to have term
as its own rule to use elsewhere.
from rust-peg.
Related Issues (20)
- warn on missing .PHONY entry for common target names HOT 1
- feature request: a way to query the current line number during parsing HOT 5
- general question about thread safety HOT 1
- Use tracing rather than println?
- Binding captured strings? HOT 6
- help with misleading expected set HOT 2
- How do I escape the dot character in [^ pat]? HOT 1
- rustc warning about unused imports HOT 1
- Make the TokenStream wrappers used internally available
- Mutual recursion with `#[cache_left_rec]` fails
- Case-insensitive literal matches throw off error position HOT 6
- `{? Err("x") }` should not be considered nullable for infinite loop check
- the `#[proc_macro]` attribute is only usable with crates of the `proc-macro` crate type HOT 2
- Automatic whitespace handling? HOT 1
- "rule" but not when HOT 2
- Error recovery when using `precedence!` HOT 2
- What about presenting on Rust Ukraine Conference 2024?
- feat: in rule where clauses support
- feat: mut variable syntax support for TaggedExpr and RuleParam HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from rust-peg.