program that is completely unrealistic. However, warning at
2 should be trivial.
Unfortunately, it isn't. This warning happens very late in the
processing, after a lot of mangling has been done. Take:
I really mean't to sat trivial by comparison :)
The point you raise about all the mangling and reordering
and other things that happen to teh code is what I feared
would cause the trouble. I just don't know enough about
the data structures involved to know if producing the
new warninging message is even possible. I dont know
how the current warning message is even calculated, and
I need to go stare at some code to find out how before
I must either give up on this idea or start asking
annoying intenals questions :)
But at least I know people aren't opposed to the idea,
so I wont be wasting my time trying.
Kean
