The difference between delete and delete[] in C++ [duplicate]

by

You delete [] when you newed an array type, and delete when you didn’t. Examples:

typedef int int_array[10];

int* a = new int;
int* b = new int[10];
int* c = new int_array;

delete a;
delete[] b;
delete[] c; // this is a must! even if the new-line didn't use [].

More Related Contents:

  1. Is delete[] equal to delete?
  2. delete vs delete[] operators in C++
  3. Is “delete this” allowed in C++?
  4. Is it safe to delete a NULL pointer?
  5. delete vs delete[] [duplicate]
  6. Why doesn’t delete set the pointer to NULL?
  7. Does delete on a pointer to a subclass call the base class destructor?
  8. What happens when you deallocate a pointer twice or more in C++?
  9. Why, really, deleting an incomplete type is undefined behaviour?
  10. How do malloc() and free() work?
  11. What is the difference between new/delete and malloc/free?
  12. C++ new int[0] — will it allocate memory?
  13. How should I write ISO C++ Standard conformant custom new and delete operators?
  14. How could pairing new[] with delete possibly lead to memory leak only?
  15. Compelling examples of custom C++ allocators?
  16. How to get available memory C++/g++?
  17. How does a C++ reference look, memory-wise?
  18. Any reason to overload global new and delete?
  19. Are memory leaks “undefined behavior” class problem in C++?
  20. Check if a pointer points to allocated memory on the heap
  21. What is the behavior of “delete” with stack objects? [duplicate]
  22. Reason why not to have a DELETE macro for C++
  23. What is “bit padding” or “padding bits” exactly?
  24. Behaviour of malloc with delete in C++
  25. How do I call the original “operator new” if I have overloaded it?
  26. How to alloc a executable memory buffer?
  27. How serious is the new/delete operator mismatch error?
  28. How does =delete on destructor prevent stack allocation?
  29. new, delete ,malloc & free
  30. Should objects delete themselves in C++?

Leave a Comment