Guys, this is a really pointless discussion.
Even if you believe (as I happen to do) that there should be a warning for case mismatches that honors scope rules and does not detect case mismatches where the different cases are used in different contexts, the fact is that Frank does not believe that is necessary or useful and so he is not interested in implementing it which is perfectly within his rights. If folks want a warning to work in a different way then they need to find a way to implement it, not just argue with Frank who clearly has thought through the issue and made his own decision. We (and he) have heard all these arguments already several times and just repeating them is unlikely to get any results.
Either write the code to produce a warning in the scope sensitive way (without impacting on the warning that Frank obviously values) or hire or find someone to do this work. You can't just expect Frank to decide to do it just because you want it done in a different way. You might have some hope of expecting that if you paid for the software, but this is open source software, and while there are lots of advantages of open source software, one of the disadvantages is that a legal user doesn't have any leverage over the developers.
Personally, I'd love to see a switch to turn on full case sensitivity, which is how I program in Metrowerks Pascal (and which as a customer I encouraged them to implement). I don't find case sensitivity a drawback because I always compile with warnings on and get rid of all warnings so there is never any issue. But then again, I am probably not going to spend the time to implement this or hire someone to do it, and I'm certainly not going to badger Frank or anyone else to do it.
So lets just drop the subject unless someone wants to volunteer to put some effort in to doing something constructive about it...? Peter.