On Tue, Dec 6, 2011 at 2:13 PM, Dave Korn <dave.korn.cyg...@gmail.com> wrote: > 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?
No. If it were we would be warning for conditionally uninitialized uses in the early uninitialized warning pass which we don't do because of the way too many false positives. Richard. > cheers, > DaveK
