LCS2016_055a_History < P1076

P1076 Web>VHDL2017>LCS2016_055a>LCS2016_055a_History (2017-07-19, JimLewis) (raw view)EditAttach
---+ Language Change Specification for Syntax regularization for endings
---+ Proposal

---++ 

| <sticky><b>LCS Number:</b></sticky> | LCS-2016-055a History |
| <sticky><b>Version:</b></sticky>  | 1 |
| <sticky><b>Date:</b></sticky>  | 05-March-2017 |
| <sticky><b>Status:</b></sticky>  | Voting |
| <sticky><b>Author:</b></sticky>  | Ryan Hinton %BR% Jim Lewis |
| <sticky><b>Email:</b></sticky>  | [[Main.RyanHinton]] %BR% [[Main.JimLewis]] |
| <sticky><b>Source Doc:</b></sticky> | [[SyntaxRegularlization][Syntax regularization - end]] |
| <sticky><b>Summary:</b></sticky>  | Make syntax for component declatations more similar to entity statements |
| <sticky><b>Derivative of 055 </b></sticky>  | [[TopLCS2016_055][LCS_2016_055]] |

---+++ Voting Results: Cast your votes here

Yes:
   1 %USERSIG{JimLewis - 2017-03-05}%
   1 %USERSIG{ThomasPreusser - 2017-03-06}%
   1 %USERSIG{MartinZabel - 2017-03-06}% - ver 1
   1 %USERSIG{FarrellOstler - 2017-03-06}%
   1 %USERSIG{MartinThompson - 2017-03-07}%

No:

Abstain:
   1 %USERSIG{BrentHahoe - 2017-03-06}% - ver 1 [[#BrentHahoe20170306][Comment below]]



---++ Comments

#BrentHahoe20170306
As has been stated by many others, optional keywords after the '<b>end</b>' keyword is historically a bad decision IMHO. However, optional simple names makes sense.

I do not like this as a concept but will not block it, hence my abstention.  

(Ditto for optional '<b>is</b>' keyword as well.)

-- %BUBBLESIG{BrentHahoe - 2017-03-06}%

@Brent: Thanks for not blocking. Your concerns are shared by many others. This is why this condensed LCS only addresses the discrepancy between the obviously closely related declarations of entities and components.

-- %BUBBLESIG{ThomasPreusser - 2017-03-06}%
%COMMENT%
Topic revision: r1 - 2017-07-19 - 10:05:42 - JimLewis
P1076