On 05/12/2011 21:43, Jeff Law wrote: > When the uninitialized & initialized to 10 paths meet, the compiler > (correctly) pretends the value for the uninitialized path is 10 as > well.
Wouldn't that be a good point at which to issue an uninitialised-use warning?
cheers,
DaveK
