In C++11 when I allocate a dynamic array using T *array = new T[n];
it's already zeroed (using gcc 4.7.2, Ubuntu 12.10 64bit).
Edit: I've checked that for T = int
.
gcc cxx-flags: -std=gnu++11 -O3 -ffast-math -fno-rtti
§ 5.3.4
If the new-initializer is omitted, the object is default-initialized (8.5); if no initialization is performed, the object has indeterminate value.
new-initializer is the ()
in new T[] ()
, which you have omitted.
§ 8.5 / 6
To default-initialize an object of type T means:
— if T is a (possibly cv-qualified) class type (Clause 9), the default constructor for T is called (and the initialization is ill-formed if T has no accessible default constructor);
— if T is an array type, each element is default-initialized;
— otherwise, no initialization is performed.
int[] is default initialized -> each element is default-initialized.
"Is this forced by the C++11 specification?": "no initialization is performed", so no, zeroing is not forced if T has no zeroing constructor (i.e. T is a POD). For T=int, no zeroing has to be performed.
Why is it zero anyway? If your program allocates new memory from the operating system, the OS zeroes the new memory for you. It would be very dangerous, if you could read memory of another program, which possibly stores sensible data. However, if you write into that memory, free it and allocate some of it again, it should not be zeroed.
It will not be initialized (still calling the constructor if T is a class, of course). To force value-initialization (which is a name that to newbies can be misleading - let's call it zero-initialization which it is for primitive types like int
), do
new T[N]()
That is, just put a pair of parenthesis.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With