I have to agree with Mike. If your code is such a tangled mess of spaghetti that you can't tell in what order a variable is being written to, or read from, then you've got bigger problems than trying to decipher an error message. I suppose that if you have really convoluted logic in the code, it might be possible to fool the compiler into thinking a variable is uninitialized, when it's not. If I were writing a compiler, I'd be conservative about assuming whether or not a variable has a value, and issue a WARNING (not an error) that I suspect the worst.
Mike Kershaw wrote: > While there are some obtuse ways to make it so the variable really does > have legit content in it and the compiler thinks it doesn't, it's > generally a coding error. > > _______________________________________________ Mid-Hudson Valley Linux Users Group http://mhvlug.org http://mhvlug.org/cgi-bin/mailman/listinfo/mhvlug Upcoming Meetings (6pm - 8pm) MHVLS Auditorium Jun 4 - Sqeak! and eToys Jul 2 - KVM (Tenative) Aug 6 - Zenos Sep 3 - TBD
