Date

- 26 August 2014

Attendees

Attendees, you will be considered present in this virtual meeting if you enter your vote in the table below. If you have no opinion on the change, enter "present".

Preamble

The SAT met on 2014-07-15 and decided to recommend that the coding standards be updated as follows:

  1. : Change both C++ and Python standards to say that developers SHOULD use the minimum number of parentheses needed for syntactic correctness and readability.
  2. : Change the Python standard to parallel the C++ standard by stating that whitespace SHOULD be omitted around math operators "*" and "/" and (Python-only) "**" and "//".
  3. : Change both the C++ and Python standards to state that whitespace SHOULD be omitted around math operator "%".

These changes to the existing Standards have been reviewed for technical merit and approved by the SAT. The

Goals

The TCT will now:

Analysis

Robyn's opinion on the impact upon cost and schedule of accepting each of these changes  is that there would be no tangible impact.  The rule is a  'SHOULD' so there would be no retrofitting of old code and there is no additional cost to omit superfluous characters.

Discussion items

WhoProposalsComment                              Yes/No/Here
Unknown User (robyn)
  1. use min amount of parens needed
  2. omit whitespace around ops: *, /, *, //
  3. omit whitespace around op: %
  1. .
  2. .
  3. .
  1. yes
  2. yes
  3. yes
Jacek Becla
  1. use min amount of parens needed
  2. omit whitespace around ops: *, /, *, //
  3. omit whitespace around op: %
  1. .
  2. .
  3. .
  1. .
  2. .
  3. .

 

Unknown User (ciardi)
  1. use min amount of parens needed
  2. omit whitespace around ops: *, /, *, //
  3. omit whitespace around op: %
  1. .
  2. .
  3. .
  1. Here
  2. Here
  3. Here

 

Andrew Connolly
  1. use min amount of parens needed
  2. omit whitespace around ops: *, /, *, //
  3. omit whitespace around op: %
  1. .On travel 'til Sept 1.
  2. .
  3. .
  1. .
  2. .
  3. .

 

Gregory Dubois-

Felsmann

  1. use min amount of parens needed
  2. omit whitespace around ops: *, /, *, //
  3. omit whitespace around op: %
  1. .
  2. .
  3. .
  1. .
  2. .
  3. .

 

Frossie Economou
  1. use min amount of parens needed
  2. omit whitespace around ops: *, /, *, //
  3. omit whitespace around op: %
  1. .
  2. .
  3. .
  1. Yes
  2. Here
  3. Here

 

Kian-Tat Lim
  1. use min amount of parens needed
  2. omit whitespace around ops: *, /, *, //
  3. omit whitespace around op: %
  1. .
  2. .
  3. .
  1. Yes
  2. Here
  3. Here
Donald Petravick
  1. use min amount of parens needed
  2. omit whitespace around ops: *, /, *, //
  3. omit whitespace around op: %
  1. .
  2. .
  3. .
  1. .
  2. .
  3. .

 

Unknown User (rlambert)
  1. use min amount of parens needed
  2. omit whitespace around ops: *, /, *, //
  3. omit whitespace around op: %
  1. .
  2. .
  3. .
  1. .
  2. .
  3. .

 

Robert Lupton
  1. use min amount of parens needed
  2. omit whitespace around ops: *, /, *, //
  3. omit whitespace around op: %
  1. .
  2. .
  3. .
  1. yes
  2. yes
  3. yes
Unknown User (xiuqin)
  1. use min amount of parens needed
  2. omit whitespace around ops: *, /, *, //
  3. omit whitespace around op: %
  1. .
  2. .
  3. .
  1. yes
  2. yes
  3. yes

 

Tally of votes:
  1. use min amount of parens needed
  2. omit whitespace around ops: *, /, *, //
  3. omit whitespace around op: %
Quorum is 6 members present
  1. 5 Yes; 2 Present.
  2. 3 Yes; 3 Present
  3. 3 Yes; 3 Present

 

Action items