-
Notifications
You must be signed in to change notification settings - Fork 2
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.
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
aslt changes + grammar + testing #53
Conversation
In case it's of interest, I'm working on a Rust parser for ASLT (based on pest). It's a work in progress but it parses a reasonable subset right now. |
@mmcloughlin, that is interesting! Do you have plans to make use of ASLp for a verification project? |
Potentially, yes. I'm trying to see if it will work for our use case at the moment. The ASLT format is quite convenient. The other thing we'll probably need is symbolic opcodes #52. |
761e7d5
to
27ff528
Compare
I've updated my Rust parser to support these new changes. All works fine. |
With the go-ahead of the Basil PR, this is scheduled for merge next Monday. |
* pp-raw for optional_else uses same format as indented_block * call pp_raw_indented_block from optional_else
ci: do not upload encodings directory
the semicolon lists seen elsewhere are the default pp-raw generated by ott. it would be much more difficult to change all other uses, so we just change this use to have a semicolon as well.
cram: add test_cntlm.t
33a31a5
to
ecfa846
Compare
Yeah, these should correspond to some simplifications over |
This PR will aim to address some inconveniences in the current aslt format (i.e. that from the AST's pp_raw methods). This should make the syntax more similar to a regular programming language (in particular, Python) and hence easier to parse with a variety of generic tools.
In the format itself,
In the ANTLR grammar,
In downstream projects,