Operator new initializes memory to zero

by

There are two versions:

wsk = new unsigned int;      // default initialized (ie nothing happens)
wsk = new unsigned int();    // zero    initialized (ie set to 0)

Also works for arrays:

wsa = new unsigned int[5];   // default initialized (ie nothing happens)
wsa = new unsigned int[5](); // zero    initialized (ie all elements set to 0)

In answer to comment below.

Ehm… are you sure that new unsigned int[5]() zeroes the integers?

Apparently yes:

[C++11: 5.3.4/15]: A new-expression that creates an object of type T initializes that object as follows: If the new-initializer is omitted, the object is default-initialized (8.5); if no initialization is performed, the object has indeterminate value. Otherwise, the new-initializer is interpreted according to the initialization rules of 8.5 for direct-initialization.

#include <new>
#include <iostream>


int main()
{
    unsigned int   wsa[5] = {1,2,3,4,5};

    // Use placement new (to use a know piece of memory).
    // In the way described above.
    // 
    unsigned int*    wsp = new (wsa) unsigned int[5]();

    std::cout << wsa[0] << "\n";   // If these are zero then it worked as described.
    std::cout << wsa[1] << "\n";   // If they contain the numbers 1 - 5 then it failed.
    std::cout << wsa[2] << "\n";
    std::cout << wsa[3] << "\n";
    std::cout << wsa[4] << "\n";
}

Results:

> g++ --version
Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr --with-gxx-include-dir=/usr/include/c++/4.2.1
Apple LLVM version 5.1 (clang-503.0.40) (based on LLVM 3.4svn)
Target: x86_64-apple-darwin13.2.0
Thread model: posix
> g++ t.cpp
> ./a.out
0
0
0
0
0
>

More Related Contents:

  1. Why should C++ programmers minimize use of ‘new’?
  2. What uses are there for “placement new”?
  3. In what cases do I use malloc and/or new?
  4. delete vs delete[] operators in C++
  5. Is it safe to delete a NULL pointer?
  6. Dynamically allocating an array of objects
  7. How could pairing new[] with delete possibly lead to memory leak only?
  8. Compelling examples of custom C++ allocators?
  9. How to get available memory C++/g++?
  10. C++, Free-Store vs Heap
  11. How does a C++ reference look, memory-wise?
  12. Any reason to overload global new and delete?
  13. How to get memory usage under Windows in C++
  14. Are memory leaks “undefined behavior” class problem in C++?
  15. Is it possible to delete a non-new object?
  16. std::vector and contiguous memory of multidimensional arrays
  17. Pointer-to-pointer dynamic two-dimensional array
  18. Can I pass std::string to a DLL?
  19. Check if a pointer points to allocated memory on the heap
  20. Reason why not to have a DELETE macro for C++
  21. Why, really, deleting an incomplete type is undefined behaviour?
  22. What is “bit padding” or “padding bits” exactly?
  23. How to alloc a executable memory buffer?
  24. How does delete work? [duplicate]
  25. If a 32-bit integer overflows, can we use a 40-bit structure instead of a 64-bit long one?
  26. “Right” way to deallocate an std::vector object
  27. Class members and explicit stack/heap allocation
  28. Why do we even need the “delete[]” operator?
  29. What happen to pointers when vectors need more memory and realocate memory?
  30. C++ delete does not free all memory (Windows)

Leave a Comment