<new>
Defines several types and functions that control the allocation and freeing of storage under program control. It also defines components for reporting on storage management errors.
Requirements
Header: <new>
Namespace: std
Remarks
Some of the functions declared in this header are replaceable. The implementation supplies a default version, whose behavior is described in this document. A program can, however, define a function with the same signature to replace the default version at link time. The replacement version must satisfy the requirements described in this document.
Members
Objects
Name | Description |
---|---|
nothrow | Provides an object to be used as an argument for the nothrow versions of new and delete . |
Typedefs
Name | Description |
---|---|
new_handler | A type that points to a function suitable for use as a new handler. |
hardware_constructive_interference_size | |
hardware_destructive_interference_size |
Functions
Name | Description |
---|---|
get_new_handler | |
launder | |
set_new_handler | Installs a user function that is called when new fails in its attempt to allocate memory. |
Operators
Name | Description |
---|---|
operator delete |
The function called by a delete expression to deallocate storage for individual of objects. |
operator delete[] |
The function called by a delete expression to deallocate storage for an array of objects. |
operator new |
The function called by a new expression to allocate storage for individual objects. |
operator new[] |
The function called by a new expression to allocate storage for an array of objects. |
Enums
Name | Description |
---|---|
align_val_t |
Classes
Name | Description |
---|---|
bad_alloc Class | The class describes an exception thrown to indicate that an allocation request did not succeed. |
bad_array_new_length Class | |
nothrow_t Class | The class is used as a function parameter to operator new to indicate that the function should return a null pointer to report an allocation failure, rather than throw an exception. |
See also
Header Files Reference
Thread Safety in the C++ Standard Library
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for