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 allocation inline
function like this:
typedef struct person {
unsigned age;
char sex;
size_t size;
char name[];
} person;
inline
person* alloc_person(int a, char s, size_t n) {
person * ret = calloc(sizeof(person) + n, 1);
if (ret) memcpy(ret,
&(person const){ .age = a, .sex = s, .size = n},
sizeof(person));
return ret;
}
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 of calloc
before doing the memcpy
. Under all systems that I programmed so far this will abort relatively nicely. Generally I think that return of malloc
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:
#define ALLOC_PERSON(A, S, N)
((person*)memcpy(calloc(sizeof(person) + (N), 1),
&(person const){ .age = (A), .sex = (S) },
sizeof(person)))
Edit: The case that this could be better than the function is when A
and S
are compile time constants. In that case the compound literal, since it is const
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.
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…