Language Change Specification for Optional Trailing Semicolons on Interface Lists

Voting Results: Cast your votes here

Yes:

1. Rob Gaddi - 2016-11-17
2. Kevin Jennings - 2016-11-22
3. Morten Zilmer - 2016-12-11
4. Martin Thompson - 2016-12-12
5. Ryan Hinton - 2016-12-14 - ver 1
6. Thomas Preusser - 2016-12-14 - ver 1
7. Lieven Lemiengre - 2017-01-09 - ver 1
8. Martin Zabel - 2017-01-12 - ver 1
9. Patrick Lehmann - 2017-01-23 - ver 1
10. Mark Zwolinski - 2017-02-23

No:

Abstain:

1. Farrell Ostler - 2017-01-12 - ver 1
2. Brent Hayhoe - 2017-02-16 Version 1 - Abstain due to lack of personal time for review.

Details of Language Change

Changes are shown in red font.

Section 6.5.6.1 Interface list

Top page 78

interface_list ::=
    interface_element { ; interface_element } [ ; ] 

-- RobGaddi - 2016-11-16

Comments

The proposal is about having optional semicolons. Why is the LCS written to define optional commas?

-- Kevin Jennings - 2016-11-03

Agreed. Split the LCS into LCS2016_071a for the semicolon and TopLCS2016_071b for the commas so they can be voted independently.

-- Rob Gaddi - 2016-11-16

Please, correct the syntax to make the final semicolon optional rather than repetitive: { ; } -> [ ; ]

-- Thomas Preusser - 2016-12-27

Good catch on optional vs. repetitive. Hopefully Rob doesn't mind that I went ahead and made this fix. I also didn't bump the revision number since the optional production is the one that I meant to vote on. In other words, I consider I'm fixing a typo, not altering the (intent) of the proposed text.

-- Ryan Hinton - 2016-12-27