> When you get this msg from a compile, you still have to find out which > uses of the variable are the offending entries. If I have 45 uses of x, > how do I find out which ones are causing the msg? > > The compiler knows, but it keeps that information to itself.
If you have 45 uses of 'x' in a routine and each one does its own initialization (i.e. you don't initialize 'x' at the top of the routine) I would argue that your code could use some refactoring. -Frank -- ---------------------------------- Frank Wallingford [EMAIL PROTECTED] _______________________________________________ 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
