Both free(NULL)
and ::operator delete(NULL)
are allowed. Does the allocator concept (e.g. std::allocator also allow deallocate(NULL,1)
, or is it required to put your own guard around it?
相关问题
- Sorting 3 numbers without branching [closed]
- How to compile C++ code in GDB?
- Why does const allow implicit conversion of refere
- thread_local variables initialization
- What uses more memory in c++? An 2 ints or 2 funct
相关文章
- Class layout in C++: Why are members sometimes ord
- How to mock methods return object with deleted cop
- Which is the best way to multiply a large and spar
- C++ default constructor does not initialize pointe
- Selecting only the first few characters in a strin
- What exactly do pointers store? (C++)
- Converting glm::lookat matrix to quaternion and ba
- What is the correct way to declare and use a FILE
You'll need to add your own check.
According to §20.4.1.1/8,
deallocate
requires:allocate
throws an exception when storage can't be given (§20.4.1.1/7). In other words,allocate
never returns 0, and thereforedeallocate
should never get a 0. Passing a 0 would lead to undefined behavior.