Difference between revisions of "Cpp Coding Standards/CLSDESIGN/NoConv"
m (Cpp Coding Standards/Class Design/NoConv moved to Cpp Coding Standards/CLSDESIGN/NoConv: consistency)
Revision as of 13:37, 22 May 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.