archives

« Bugzilla Issues Index

#4378 — 13.7.5.1: suggested restructuring of early errors

• bug_id: 4378
• creation_ts: 2015-05-26 10:06:00 -0700
• short_desc: 13.7.5.1: suggested restructuring of early errors
• delta_ts: 2015-10-10 09:03:24 -0700
• product: Draft for 7th Edition
• component: Deferred from 6th edition
• version: unspecified
• rep_platform: All
• op_sys: All
• bug_status: CONFIRMED
• priority: Normal
• bug_severity: enhancement
• everconfirmed: true
• reporter: Michael Dyck
• assigned_to: Allen Wirfs-Brock

---

• commentid: 14454
• comment_count: 0
• who: Michael Dyck
• bug_when: 2015-05-26 10:06:37 -0700

In 13.7.5.1 "Static Semantics: Early Errors",
group 1 would be easier to understand if the rules were written more like this:

- If LeftHandSideExpression is either an ObjectLiteral or an ArrayLiteral,
then
- If the lexical token sequence matched by LeftHandSideExpression
can be parsed with no tokens left over using AssignmentPattern
as the goal symbol, then
Apply the Early Error rules for AssignmentPattern to the result of
that parse.
- Else
It is a Syntax Error
- Else
- If IsValidSimpleAssignmentTarget of LeftHandSideExpression is false,
it is a Syntax Error.

- If the LeftHandSideExpression is
CoverParenthesizedExpressionAndArrowParameterList : ( Expression )
and [etc].
[This rule could be at this level or the outer level, to taste.]

I realize that no set of Early Error rules is currently written this way (though there are hints of it in 14.1.2, 14.2.1, 14.5.1, and 15.2.3.1), but I think the flat-list-of-bullets format is getting in the way of clarity here.