Add member initializer lists and ternary operators to coding standards

[ThanHenderson]

Signed-off-by: Nathan Henderson [email protected]

[ThanHenderson]

@keithc-ca I've based these changes off our discussion. Let me know if there's something else you'd be interested in adding.

[keithc-ca]

I don't think suggesting alignment is necessarily a good idea. I think the second and subsequent lines should be indented as continued lines would be (at least one tab). We might include an example that shows how all parts might be aligned by starting with the identity of the binary operator:

uint32_t result = 0
        + longVariableNameOrCalculation1
        + longVariableNameOrCalculation2
        + longVariableNameOrCalculation3;

[ThanHenderson]

I'll remove the suggestion of alignment in favour of suggesting consistent indentation. Though, I think the example of:

uint32_t result = longVariableNameOrCalculation1
            + longVariableNameOrCalculation2
            + longVariableNameOrCalculation3;

is sufficient.

[keithc-ca]

That's fine; my point, though, was that sometimes putting (what would otherwise be) the first operand on the next line is that it might clarify the relationship between the (originally) first operand and later operands.

[ThanHenderson]

Ok, I understand. Despite similarity in naming, I wasn't trying to embed any type of (special) relationship between the longVariableNameOrCalculation operands. I think I'll leave it as described in my above comment.