Difference between revisions of "Cpp Coding Standards/CLSDESIGN/NoConv"
From Apache OpenOffice Wiki
m (Cpp Coding Standards/Class Design/NoConv moved to Cpp Coding Standards/CLSDESIGN/NoConv: consistency) |
|||
| Line 1: | Line 1: | ||
Avoid implicit conversions, because they might fire in the most unexpected places (and shoot you or your fellow coder in the foot). Apart from that, they might introduce subtle ambiguities (more than one way for the compiler to get from type A to type B). Prefer explicit conversions instead, because you can control their usage. | Avoid implicit conversions, because they might fire in the most unexpected places (and shoot you or your fellow coder in the foot). Apart from that, they might introduce subtle ambiguities (more than one way for the compiler to get from type A to type B). Prefer explicit conversions instead, because you can control their usage. | ||
| + | |||
| + | [[Category:Coding Standards]] | ||
Latest revision as of 23:08, 19 July 2007
Avoid implicit conversions, because they might fire in the most unexpected places (and shoot you or your fellow coder in the foot). Apart from that, they might introduce subtle ambiguities (more than one way for the compiler to get from type A to type B). Prefer explicit conversions instead, because you can control their usage.
