If you were allowed to add another coding guideline to the 101 guidelines of the "C++ coding standards" (Herb Sutter and Andrei Alexandrescu), which would you add?
+1
A:
I vote for: "avoid considering goto, naming notation and indentation as being the subjects of coding rules"
Nicola Bonelli
2008-10-18 19:37:48
This is very similar to "don't sweat the small stuff".
Richard Corden
2008-10-21 17:48:22
A:
Rule 102: Any change to expected functionality should result in a regression test that fails.
Richard Corden
2008-10-21 18:06:56
Less experienced coders have no idea of what's "judicious" and more experienced one may have professional differences of opinion, so this falls a bit short of a useful guideline. A good guideline would define what's judicious.
DarenW
2009-01-17 01:06:38
A:
Comptrol
2009-02-19 13:52:18
A:
Prefer constructors to init()/setup() functions.
Why manipulating an object that may be in an unusable state? Isn't it better to not have it at all ?
Luc Hermitte
2009-02-19 14:57:25