Minutes for 0061: local variables

Standard: 802.1AS-2011 Clause: 10.2.6.1.1 Draft with fix: 802.1AS-Rev Status: Published
Submitter: Paul Woods Date: 2012-11-01 Rationale: 10.2.6.1.1: The name rcvdPSSync is used in 10.2.11.1.1 and 10.2.12.1.1 f...
Show Request Show Preformatted Request
Date Meeting Text Status
2012-11-13 Nov 2012 Planery It is true that fundamentally local variables in different functions or state machines can have the same name; however, it would be helpful to the user if the names of different variables were different. For example, this would facilitate searching for all instances of a variable. If we do rename variables so that variables in different functions or state machines have different names, how should we pick the new names (e.g., append the numbers 1, 2, … to each name that is a different variable?). Also, should this change go in the corrigendum or in 802.1ASbt (since it actually is not fixing something that is incorrect; rather, it is improving the document)? Technical review – is this appropriate for .1ASbt? Technical experts review
2013-01-15 Jan 2013 Interim This is actually not fixing something that is incorrect; rather, it is improving the document, so it belongs in .1ASbt However, the practice in 802.1 is to use unique names even for local variables. As a result, it is recommended to implement this improvement in .1ASbt Published
2013-03-19 Mar 2013 Plenary It is recommended to implement this improvement in .1ASbt. Draft for this document expected after next meeting. Complete then Ballot
2013-05-15 May 2013 Interim Draft for .1ASbt expected after next meeting. Complete then Ballot
2013-07-15 Jul 2013 Plenary Draft for .1ASbt expected after next meeting. Complete then Ballot
2013-09-03 Sep 2013 Interim An initial .1ASbt draft is available. However, as this is a significant change, the editor will do this last – perhaps in the next draft. Complete then Ballot
2013-11-12 Nov 2013 Plenary No update. Complete then Ballot
2014-01-22 Jan 2014 Plenary The editor is in process of implementing in collaboration with IEEE 1588 (that is in process of a revision) to get some alignment in the naming of terms. This process has identified a number of additional issues that the editor is in process of resolving as well. Complete then Ballot
2014-03-18 Mar 2014 Plenary No update. Complete then Ballot
2014-05-14 May 2014 Interim No update. Complete then Ballot

Back