Quote:Original post by doynax
I'm not exactly sure why your complier is issuing a warning though, there's nothing fundamentally bad with uninitialized values. There's even cases where you just don't care what the initial value is and still base your calculations on it. Maybe you could just disable the warning?
We are working in a big Project.
Many different programmers are hacking in the same CVS Tree.
And unitialized variables (return values, pointers, Strucs!) can sometimes cause several hours of debugging for our Support Team.
Static Variables are not an option, i usualy try to avoid them.
Quote:No it doesn't. It sets all members to zero. If you miss off excess elements at the end of the initialiser list it sets the remaining elements to a zero of the appropriate type. Even if they are non-statically allocated structs
And thats exactly what i wanted to hear :)
Thanks
Lazzar
---------------------------------------------------------if god gave us the source code, we could change the world!