In the C++ programming language, placement syntax allows programmers to explicitly specify the memory management of individual objects — i.e. their "placement" in memory. Normally, when an object is created dynamically, an allocation function is invoked in such a way that it will both allocate memory for the object, and initialize the object within the newly allocated memory. The placement syntax allows the programmer to supply additional arguments to the allocation function. A common use is to supply a pointer to a suitable region of storage where the object can be initialized, thus separating memory allocation from object construction.
The "placement" versions of the [[new (C++)|new]] and [[delete (C++)|delete]] operators and functions are known as placement new and placement delete. A new expression, placement or otherwise, calls a new function, also known as an allocator function, whose name is operator new. Similarly, a delete expression calls a delete function, also known as a deallocator function, whose name is operator delete.
Any new expression that uses the placement syntax is a placement new expression, and any operator new or operator delete function that takes more than the mandatory first parameter (
In earlier versions of C++ there was no such thing as placement new; instead, developers used explicit assignment to this within constructors to achieve similar effect. This practice has been deprecated and abolished later, and the third edition of The C++ Programming Language doesn't mention this technique.
The Standard C++ syntax for a non-placement new expression is
new ''new-type-id'' (''optional-initializer-expression-list'')
The placement syntax adds an expression list immediately after the new keyword. This expression list is the placement. It can contain any number of expressions.
new (''expression-list'') ''new-type-id'' (''optional-initializer-expression-list'')
The placement new functions are overloads of the non-placement new functions. The declaration of the non-placement new functions, for non-array and array new expressions respectively, are:
The Standard C++ library provides two placement overloads each for these functions. Their declarations are:
In all of the overloads, the first parameter to the operator new function is of type
There are also placement delete functions. They are overloaded versions of the non-placement delete functions. The non-placement delete functions are declared as:
The Standard C++ library provides two placement overloads each for these functions. Their declarations are:
In all of the overloads, the first parameter to the operator delete function is of type
For both the new and the delete functions, the functions are global, are not in any namespace, and do not have static linkage.
Placement syntax has four main uses: default placement, preventing exceptions, custom allocators, and debugging.
The placement overloads of operator new and operator delete that employ an additional
There are various uses for default placement.
Bjarne Stroustrup originally observed, in his book The Design and Evolution of C++, that pointer placement new is necessary for hardware that expects a certain object at a specific hardware address. It is also required for the construction of objects that need to reside in a certain memory area, such as an area that is shared between several processors of a multiprocessor computer.
Other uses, however, include calling a constructor directly, something which the C++ language does not otherwise permit.
The C++ language does allow a program to call a destructor directly, and, since it is not possible to destroy the object using a delete expression, that is how one destroys an object that was constructed via a pointer placement new expression. For example:
Placement new is used when you do not want operator new to allocate memory (you have pre-allocated it and you want to place the object there), but you do want the object to be constructed. Examples of typical situations where this may be required are:
std::vector<> (see std::vector<>::reserve).The basic problem is that the constructor is a peculiar function; when it starts off, there is no object, only raw memory. And by the time it finishes, you have a fully initialized object. Therefore, i) The constructor cannot be called on an object ii) However, it needs to access (and initialize) non-static members. This makes calling the constructor directly an error. The solution is the placement form of operator new.
This operator is implemented as:
Normally, the (non-placement) new functions throw an exception, of type std::bad_alloc, if they encounter an error, such as exhaustion of all available memory. This was not how the functions were defined by Stroustrup's Annotated C++ Reference Manual, but was a change made by the standardization committee when the C++ language was standardized. The original behaviour of the functions, which was to return a
Programmers who wish to do this in their programs must include the Standard C++ library header <new> in the source code. This header declares the global std::nothrow object, which is of type std::nothrow_t (also declared in the header), which is used to call the overloaded new functions that are declared as taking
struct T ;
int main
Placement syntax is also employed for custom allocators. This does not use any of the allocator and deallocator functions from the Standard C++ library header <new>, but requires that programmers write their own allocation and deallocation functions, overloaded for user-defined types. For example, one could define a memory management class as follows:
class A ;
And define custom placement allocation and deallocation functions as follows:
void operator delete(void* p, A& arena)
The program would employ the placement syntax to allocate objects using different instances of the A class as follows:
Destroying an object whose storage is allocated in such a fashion requires some care. Because there is no placement delete expression, one cannot use it to invoke the custom deallocator. One must either write a destruction function that invokes the custom deallocator, or call the placement delete function directly, as a function call.
The former would resemble:
The latter would involve simply writing the destructor invocation and delete function call into the program:
A common error is to attempt to use a delete expression to delete the object. This results in the wrong operator delete function being called. Dewhurst recommends two strategies for avoiding this error. The first is to ensure that any custom allocators rely upon the Standard C++ library's global, non-placement, operator new, and are thus nothing more than simple wrappers around the C++ library's memory management. The second is to create new and delete functions for individual classes, and customize memory management via class function members rather than by using the placement syntax.
Placement new can also be used as a simple debugging tool, to enable programs to print the filename and line number of the source code where a memory allocation has failed. This does not require the inclusion of the Standard C++ library header <new>, but does require the inclusion of a header that declares four placement functions and a macro replacement for the new keyword that is used in new expressions. For example, such a header would contain:
void* operator new(std::size_t size, const char* file, int line);void* operator new[](std::size_t size, const char* file, int line);void operator delete(void* p, const char* file, int line);void operator delete[](void* p, const char* file, int line);
This would be employed in a program as follows:
The custom-written placement new functions would then handle using the supplied file and line number information in the event of an exception. For example:
class NewError ;
void *operator new(std::size_t size, const char* file, int line)
As noted above, there is no placement delete expression. It is not possible to call any placement operator delete function using a delete expression.
The placement delete functions are called from placement new expressions. In particular, they are called if the constructor of the object throws an exception. In such a circumstance, in order to ensure that the program does not incur a memory leak, the placement delete functions are called. A placement new expression first calls the placement operator new function, then calls the constructor of the object upon the raw storage returned from the allocator function. If the constructor throws an exception, it is necessary to deallocate that storage before propagating the exception back to the code that executed the placement new expression, and that is the purpose of the placement delete functions.
The placement delete function that is called matches the placement new function that was invoked by the placement new expression. So, for example, if the following code is executed, the placement delete function that is called will be operator delete(void *, const A &):
struct A ;struct E ;
class T ;
void * operator new(std::size_t, const A&)
void operator delete(void*, const A&)
int main
This is why the pointer placement delete functions are defined as no-operations by the Standard C++ library. Since the pointer placement new functions do not allocate any storage, there is no storage to [1] be deallocated in the event of the object's constructor throwing an exception.
If no matching placement delete function exists, no deallocation function is called in the event of an exception being thrown by a constructor within a placement new expression. There are also some (older) C++ implementations that do not support placement delete (which, like the exception-throwing allocator functions, were an addition made to C++ when it was standardized) at all. In both such situations, an exception being thrown by a constructor when allocating using a custom allocator will result in a memory leak. (In the case of the older C++ implementations, a memory leak will also occur with non-placement new expressions.)
Placement new expressions are vulnerable to security exploits. In 2011, Kundu and Bertino demonstrated some of the exploits on placement new. Some of the attacks are buffer overflow attacks, object overflow, selective stackguard overriding, virtual pointer subterfuge, memory misalignment attacks. In 2015, GCC released a patch[2] based on the findings in.