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

Clarify language in 8.3.5 <condition>. #988

Closed
skynavga opened this issue Sep 9, 2018 · 2 comments
Closed

Clarify language in 8.3.5 <condition>. #988

skynavga opened this issue Sep 9, 2018 · 2 comments

Comments

@skynavga
Copy link
Collaborator

skynavga commented Sep 9, 2018

Improve language by changing

If a <condition> value contains a function-expression non-terminal, then it must take the form of a expression.

to

A <function-expression> that appears in a <condition> value must take the form of a <condition-function> expression.

@nigelmegitt
Copy link
Contributor

It'd be useful to explain the motivation for this change. Both the existing and proposed variants do not seem problematic. The phrase "non-terminal" doesn't seem to be helpful, so happy to remove it.

@nigelmegitt
Copy link
Contributor

nigelmegitt commented Sep 10, 2018

See motivation from @skynavga at #996 (comment) :

@palemieux thought 'it' could refer to <condition> (I didn't) and didn't like 'non-terminal' either

skynavga added a commit that referenced this issue Sep 11, 2018
Clarify language regarding function-expression in @condition (#988).
@skynavga skynavga removed their assignment Sep 11, 2018
@skynavga skynavga removed the pr open label Sep 11, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants