Why is there no reallocation functionality in C++ allocators?

by

From:
http://www.sgi.com/tech/stl/alloc.html

This is probably the most questionable
design decision. It would have
probably been a bit more useful to
provide a version of reallocate that
either changed the size of the
existing object without copying or
returned NULL. This would have made it
directly useful for objects with copy
constructors. It would also have
avoided unnecessary copying in cases
in which the original object had not
been completely filled in.

Unfortunately, this would have
prohibited use of realloc from the C
library. This in turn would have added
complexity to many allocator
implementations, and would have made
interaction with memory-debugging
tools more difficult. Thus we decided
against this alternative.

More Related Contents:

  1. Is it safe to realloc memory allocated with new?
  2. Avoid memory leaks in C++ Pointers [closed]
  3. C++ – destructors [closed]
  4. In what cases do I use malloc and/or new?
  5. delete vs delete[] operators in C++
  6. Is it safe to delete a NULL pointer?
  7. Operator new initializes memory to zero
  8. delete vs delete[] [duplicate]
  9. Global memory management in C++ in stack or heap?
  10. How to get memory usage at runtime using C++?
  11. How do you ‘realloc’ in C++?
  12. Why doesn’t delete set the pointer to NULL?
  13. Smart pointers: who owns the object? [closed]
  14. Is there a reason to call delete in C++ when a program is exiting anyway?
  15. Why is stack memory size so limited?
  16. How to properly replace global new & delete operators
  17. Allocating more memory than there exists using malloc
  18. How do you determine the size of an object in C++?
  19. Initial capacity of vector in C++
  20. What do I need to do before deleting elements in a vector of pointers to dynamically allocated objects?
  21. Implementing a std::vector like container without undefined behavior
  22. Call destructor and then constructor (resetting an object)
  23. Memory allocation and deallocation across dll boundaries
  24. How does delete work? [duplicate]
  25. How to track memory allocations in C++ (especially new/delete)
  26. How to check memory allocation failures with new operator?
  27. Memory-efficient C++ strings (interning, ropes, copy-on-write, etc) [closed]
  28. new, delete ,malloc & free
  29. C++ is it necessary to delete dynamically allocated objects at the end of the main scope?
  30. Should objects delete themselves in C++?

Leave a Comment