I have built a working C library, that uses constants, in header files defined as
typedef struct Y {
union {
struct bit_field bits;
uint8_t raw[4];
}
I had the same problem. For C89 the following is true:
With C89-style initializers, structure members must be initialized in the order declared, and only the first member of a union can be initialized
I found this explanation at: Initialization of structures and unions
I decided to choose the following path.
.member
initialization.static const struct Foobar
initialization of membersInstead declare the global variable:
extern "C" {
extern const struct Foobar foobar;
}
and initialize it in a global section:
struct Foobar foobar = { 0, 0, 0, 0 };
and instead of bugging the C++ compiler with modern ANSI C99 syntax I let the linker do the work be demangling C symbols.
I believe that C++11 allows you to write your own constructor like so:
union Foo
{
X x;
uint8_t raw[sizeof(X)];
Foo() : raw{} { }
};
This default-initializes a union of type Foo
with active member raw
, which has all elements zero-initialized. (Before C++11, there was no way to initialize arrays which are not complete objects.)