hydroper commented on issue #237:
URL:
https://github.com/apache/royale-compiler/issues/237#issuecomment-2081034541
I've done a few definitive changes so far.
# Function bodies
* Function bodies consisting of an expression: an expression is consumed
only if one of the following conditions are met:
* The offending token is inline.
* The offending token of the expression is in a line whose indentation is
higher than that of the previous token.
* The offending token of the expression is `(`.
This is to avoid issues with expressions not belonging to the body of a
`native` or `abstract` method.
# Removed Syntax
I have removed the new `embed { ... }` expression as it is inconsistent with
the `Embed` meta-data, and it is not very useful in practice, I realize it
myself.
# Parser Updates
I've finished a CSS parser (I'm backwards to Royale in terms of function
calls such as `{x}-gradient(...)`, but I believe it's straightforward to
support their syntax).
I've made the diagnostics very flexible as well, taking arbitrary arguments
without much cumbersome in Rust (`diagarg![...]` macro), and approximated them
more to Flex messages.
There have been a number of improvements, error recovery reinforcements, bug
fixes, interface changes, name changes. A lot of refactoring and lots of weird
things have gone off.
Now I think it's good for a 1.0 release, what do you think? I'd like to
provide a compiler crate on top of that, but I'm thinking a bit yet..
Also, if you want a Rust introduction, I've wrote a detailed
[quickstart](https://github.com/hydroper/as3parser/wiki/Rust-for-ActionScript-developers)
at the wiki.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@royale.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
