@fcarney
Yes, and also as per reading the link you referenced, your understanding is correct. Static/global storage declarations will be initialized to 0, but local/stack will be uninitialized. This would be just as true if your variable was int instead of struct ....
I'm not sure why you cannot think how to test this. I have gone to http://cpp.sh and pasted:
// Example program
#include <iostream>
#include <string>
struct SomeStruct
{
int somevalue;
} buncha_structs[256];
int main()
{
SomeStruct local_structs[256];
std::cout << local_structs[1].somevalue << std::endl;
std::cout << buncha_structs[1].somevalue << std::endl;
}
available as http://cpp.sh/5gbae (don't know how long that link is valid).
Note that I think you did not intend the typedef in your code. With the typedef, your buncha_structs is a type not a variable. I have removed the typedef to give you a global variable, which I think is what you intended.
The above reliably outputs 0 for the second, global variable case, but outputs a "random", changing number each time for the first, local case. You should also see that it shows an "uninitialized" warning message against your use in the local variable case.
