well I want
to know that a value I expect to be initialised is undefined, so turning off this specific warning wont happen.
But much more importantly, and even of concern to you, Zaxo, is I want to know where it is happening - the sample code is specifically designed(!) to provoke the error that the wrong line number is reported - the fact that the expression's are bogus is unimportant. Imagine how much time you, Zaxo, would waste if you looked for a warning reported on line 100, when the real cause is line 400. Or that the warning is reported correctly on one platform, but is misreported on another - is it one warning?two different ones?
I want information from the monks about the warning being reported on the incorrect line, not that the code to provoke the error is deficient in some unrelated way.