warning: missing braces around initializer about exengine HOT 4 CLOSED

Great I have submitted a pull request for this, this was not really a pressing issue but I will try to help where I can..

from exengine.

GLint ex_uniform_map[256][256] = {0}; 

What actually happens here is that the first element of the array is set to the value in the braces, in this case it would be 0. After this, the rest of the array is initialized to 0 by default. If I where to set that value to say, 1. The first element of the array would be 1 while the rest would again be initialized to 0 by default.

Your solution does indeed remove the warning, without any logic actually changing.

note that = {0} has been valid since c98, I believe

from exengine.

Ah alright if it's valid c I guess it's fine. And I will close this comment for that.
However one could still argue that the double curly bracket is "more readable", hence why it is probably a compile warning over a compile error.

from exengine.

@subject546 feel free to submit a PR though, if not I'll get around to it eventually. I'm currently focusing on other aspects of the engine.

from exengine.