--- On Wed, 17/2/10, okias <d.okias@xxxxxxxxx> wrote:
> You have probably right, but when I
> use my testing program:
>
> #include <stdio.h>
> main() {
> int a;
> printf("%i\n", a);
> a |= 22;
> printf("%i\n", a);
> }
>
> Output is:
> 0
> 22
>
> it look correct to me
It is wrong - you are relying on and depending on the compiler zero'ing uninitialized variables for you - which, depends on which compiler you are using, optimization level, etc, may or may not happen. (some compiler does that, under some conditions/optimizations, but you cannot depend on that).
>
>
> 2010/2/17 Johannes Berg <johannes@xxxxxxxxxxxxxxxx>:
> > On Wed, 2010-02-17 at 19:34 +0100, okias wrote:
> >> I did test on small C program, and "int a" is
> equal to int a = 0; so
> >> it should be fine, but maybe I'm wrong.
> >
> > It's not equal. It will be uninitialised stack garbage
> if you don't
> > initialise it.
> >
> > johannes
> >
>
>
>
> --
> Jabber/XMPP: okias@xxxxxxxxxxx
> SIP VoIP: sip:17474537254@xxxxxxxxxxxxxxxxxxxx
>
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
