Numbers in freshly declared arrays, what do they mean?

Question

Can somebody please explain the difference in initializing the arrays between the presented two ways and why the initial readings don't always equal to 0 after declaring an array? The readings in the second array actually change from launch to launch.

https://sololearn.com/compiler-playground/cpbzDYYkvVTA/?ref=app

Answer 1

They are both unitialized. It just happens that the first one got 0's.

you can write
int *p = new int[size]();
int arr[size]{};
to create 0 initialized array

also, the second way is better because you have to free up every new call...
delete[] p;
p = nullptr;
to avoid memory leaks and prevent access .

Answer 2

Wow, two curly brackets is all it takes to fix. Thank you, that's super compact!

Answer 3

They are both unitialized. It just happens that the first one got 0's.

you can write
int *p = new int[size]();
int arr[size]{};
to create 0 initialized array

also, the second way is better because you have to free up every new call...
delete[] p;
p = nullptr;
to avoid memory leaks and prevent access .

Answer 4

Nirmit
I posted that,
and so... what is it that you want to add to this? just curious about the copy-paste post.