I have the following structure
typedef struct _person {
int age;
char sex;
char name[];
}person;
I have done some basic internet search (but unsuccessful) on how to create an instance and initialize a structure with a flexible array member without using malloc()
.
For example: for normal structures like
struct a {
int age;
int sex;
};
We can create an instance of struct a
and initialize it like
struct a p1 = {10, 'm'};
But for structures with flexible array in it (like _person
as mentioned above) how can we create an instance and initialize like how we do it for normal structures
?
Is it even possible? If so, how do we pass the array size during the initialization and the actual value to be initialized?
(or)
Is it true that the only way to create a structure with flexible array is using malloc()
as mentioned in C99 specification - 6.7.2.1 Structure and union specifiers - point #17
?!
A structure type with a flexible array member can be treated as if the flexible array member were omitted, so you can initialize the structure like this.
However, there are no members of the flexible array allocated and any attempt to access a member of the flexible array or form a pointer to one beyond its end is invalid. The only way to create an instance of a structure with a flexible array member which actually has elements in this array is to dynamically allocate memory for it, for example with
malloc
.No, flexible arrays must always be allocated manually. But you may use
calloc
to initialize the flexible part and a compound literal to initialize the fixed part. I'd wrap that in an allocationinline
function like this:Observe that this leaves the check if the allocation succeeded to the caller.
If you don't need a
size
field as I included it here, a macro would even suffice. Only that it would be not possible to check the return ofcalloc
before doing thememcpy
. Under all systems that I programmed so far this will abort relatively nicely. Generally I think that return ofmalloc
is of minor importance, but opinions vary largely on that subject.This could perhaps (in that special case) give more opportunities to the optimizer to integrate the code in the surroundings:
Edit: The case that this could be better than the function is when
A
andS
are compile time constants. In that case the compound literal, since it isconst
qualified, could be allocated statically and its initialization could be done at compile time. In addition, if several allocations with the same values would appear in the code the compiler would be allowed to realize only one single copy of that compound literal.There are some tricks you can use. It depends on your particular application.
If you want to initialise a single variable, you can define a structure of the correct size:
The problem is that you have to use pointer casting to interpret the variable as "person"(e.g. "*(person *)(&your_variable)". But you can use a containing union to avoid this:
so, your_var.p is of type "person". You may also use a macro to define your initializer, so you can write the string only once:
Another problem is that this trick is not suitable to create an array of "person". The problem with arrays is that all the elements must have the same size. In this case it's safer to use a
const char *
instead of achar[]
. Or use the dynamic allocation ;)