Skip to content
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

Documentation issues #125

Open
davidcok opened this issue Jan 13, 2023 · 0 comments
Open

Documentation issues #125

davidcok opened this issue Jan 13, 2023 · 0 comments

Comments

@davidcok
Copy link

On reading the AGREE documentation in GitHub on Expressions (https://github.com/loonwerks/AGREE/blob/master/com.rockwellcollins.atc.agree.doc/src/user-guide/03.07-Expressions.markdown)

I note:

  • The grammar listing does not list array-index expression; and I see from the text grammar that there are a number of other productions missing -- forall, exists to name two
  • The formatting of the precedence listing is garbled, at least when viewed in GitHub
  • The precedence of if-then-else is stated as higher than that of operators. That is odd and would mean that
    if a then b else c + d would parse as (if a then b else c) + d
    Rather, the Agree.xtext gives if-then-else a high precedence on the left (where it doesn't matter because of the keyword) but the lowest precedence of all on the right -- since the IfThenElseExpr production ends with c=Expr, which is more or less what most would expect, but not clear from the documentation (though the example is correct)

And two questions:
a) Is <> entirely equivalent to != ?
b) Is <=> entirely equivalent to = except for precedence?

Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant