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 a
Kean Johnston <[EMAIL PROTECTED]> writes:
>> A common situation would be:
>> if (condition) {
>> flag = 1
>> msg = "Hello World";
>> } else
>> flag = 0; [1]
>> ...
>> if (flag)
>> printf ("I say, %s\n", m
Kean Johnston wrote:
>> A common situation would be:
>>
>> if (condition) {
>> flag = 1
>> msg = "Hello World";
>> } else
>> flag = 0;[1]
>> ...
>> if (flag)
>> printf ("I say, %s\n", msg);[2]
>>
>> Point [1] is where I "fail" to init
A common situation would be:
if (condition) {
flag = 1
msg = "Hello World";
} else
flag = 0; [1]
...
if (flag)
printf ("I say, %s\n", msg); [2]
Point [1] is where I "fail" to in
Kean Johnston wrote:
> Hello everyone,
>
> There is a warning message I would dearly love to see improved
> a little. Its the one where you use a variable without it being
> initialized first:
>
> foo.c:123: warning: `foo' might be used unitialized in this function
>
> Obviously, there was som
