> The goal should not be to pacify compilers' false alarms. The goal should be > to have code that works correctly, is easy to understand, is efficient, etc.
In my personal code, when gcc complains about an uninitialized variable, even if the code is correct, I usually either add an initialization or restructure the code. If the control flow is complicated enough that gcc can't follow it, usually the code takes some effort to understand, debugging in the future could waste time verifying that the variable is initialized in all flow paths, and changes to the code could accidentally create flow paths that leave the variable uninitialized. William