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.

I now have found a way to identify them with a program (without my
writing a dataflow analysis), but before I write it, if anyone already has 
such a program, please tell me now so I don't do any unnecessary work.

Lex
_______________________________________________
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

Reply via email to