erik quanstrom wrote:
It's a pity. In other - more complicated - situations I found such
warnings appropriate and very helpful.
Could that case be recognised during the variable-scope analysis on the
intermediate format (tuples ?) ?
I don't remember what D.Gries and others said about and I don't know the
8c internals at all.
It's just an academic question I do for cultural interest.
IMHO 8c is better than gcc even if sometimes it wrongly complains about
variables use.
sure, one could perform all sorts of analysis on the code.
but i think that would be beside the point.
? ... sicerely, I don't understand the exact meaning of these sentences
in this context.
Please, could you express the same concept with different words ?
i find that code that is subtle
enough to evoke a warning often needs to be simplified
for the benefit of other humans — or even the author in
a week.
Absolutely true.
But I got a subtle compiler message about a very very simple and short
piece of code.
in your case, you can either provide a dummy assignment
or use SET(var) to inform 8c that it can forget about that
warning.
I didn't know SET(var) so I used a dummy assignment, as you can see in
my original mail.
Both seems to me a medicine worst than the disease. Personal opinion, of
course.
adriano
