C++ new int[0] — will it allocate memory?

by

From 5.3.4/7

When the value of the expression in a direct-new-declarator is zero, the allocation function is called to allocate an array with no elements.

From 3.7.3.1/2

The effect of dereferencing a pointer returned as a request for zero size is undefined.

Also

Even if the size of the space requested [by new] is zero, the request can fail.

That means you can do it, but you can not legally (in a well defined manner across all platforms) dereference the memory that you get – you can only pass it to array delete – and you should delete it.

Here is an interesting foot-note (i.e not a normative part of the standard, but included for expository purposes) attached to the sentence from 3.7.3.1/2

[32. The intent is to have operator new() implementable by calling malloc() or calloc(), so the rules are substantially the same. C++ differs from C in requiring a zero request to return a non-null pointer.]

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. Is “delete this” allowed in C++?
  5. Will new return NULL in any case?
  6. How to initialise memory with new operator in C++?
  7. Is it possible to delete a non-new object?
  8. Call destructor and then constructor (resetting an object)
  9. new, delete ,malloc & free
  10. When does invoking a member function on a null instance result in undefined behavior?
  11. How do malloc() and free() work?
  12. What is the difference between new/delete and malloc/free?
  13. Is delete[] equal to delete?
  14. Why does the use of ‘new’ cause memory leaks?
  15. How should I write ISO C++ Standard conformant custom new and delete operators?
  16. Why is my program slow when looping over exactly 8192 elements?
  17. What is difference between instantiating an object using new vs. without
  18. General guidelines to avoid memory leaks in C++ [closed]
  19. Is there any guarantee of alignment of address return by C++’s new operation?
  20. How to know if a pointer points to the heap or the stack?
  21. Why does std::cout convert volatile pointers to bool?
  22. Does delete on a pointer to a subclass call the base class destructor?
  23. What is going on with ‘gets(stdin)’ on the site coderbyte?
  24. What is the behavior of “delete” with stack objects? [duplicate]
  25. When to use new and delete
  26. Does this type of memory get allocated on the heap or the stack?
  27. How do I call the original “operator new” if I have overloaded it?
  28. When do programmers use Empty Base Optimization (EBO)
  29. vector memory allocation strategy
  30. Memory-efficient C++ strings (interning, ropes, copy-on-write, etc) [closed]

Leave a Comment