Language Change Specification for Fix Generate Statement

LCS Number:	LCS-2016-I11
Version:	2
Date:	17-Mar-2017
Status:	Voting
Author:	Patrick Lehmann and Jim Lewis
Email:	Main.PatrickLehmann Main.JimLewis
Source Doc:	Fix Generate Statement
Summary:

Voting Results: Cast your votes here

Yes:

1. Jim Lewis - 17-Mar-2017 ver 2
2. Patrick Lehmann - 17-Mar-2017 ver 2
3. Lieven Lemiengre - 23-Mar-2017 ver 2
4. %USERSIG{RobGaddi - 2017-03-23} ver 2

No:

Abstain:

Revision History

Revision 2: 17-Mar-2017 Updated 12.1

Revision 1: 13-Mar-2017 Initial

Style Notes

Changes are shown in red font. Deletions are crossed out. Editing notes in green font.

Reviewing Notes

Issue A: Edit done in 12.1 page 185 Issue B: No action requested Issue C: Edit in 11.1 page 169 Issue D: For Generate: Lots of text in the LRM could be improved. This one currently has a commonly understood meaning and no implementation issues. Editing deferred to a future version. Issue E: Not an ISAC issue. Forward to next language revision

Details of Language Change

11.1

Last paragraph of section on page 169

All concurrent statements may be labeled. Similarly, if generate and case generate statements may optionally contain alternative labels. Such labels are implicitly declared at the beginning of the declarative part of the innermost enclosing entity declaration, architecture body, block statement, or generate statement.

12.1

Alphabetic list on page 185

l) A for generate statement
m) The generate statement body of an if or case generate
n m) ...

Comments

?? Where should alternative labels be declared?? Does this match where generate labels go?

-- Jim Lewis - 2017-03-21