Home/ Questions/Q 869953
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-15T10:23:26+00:00

Both free(NULL) and ::operator delete(NULL) are allowed. Does the allocator concept (e.g. std::allocator also

  • 0

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?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You’ll need to add your own check.

    According to §20.4.​1.1/8, deallocate requires:

    p shall be a pointer value obtained from allocate(). n shall equal the value passed as the
    first argument to the invocation of allocate which returned p.

    allocate throws an exception when storage can’t be given (§20.4.​1.1/7). In other words, allocate never returns 0, and therefore deallocate should never get a 0. Passing a 0 would lead to undefined behavior.

    • 0