Re: [boost] exception handling anti-patterns in documentation

On Sun, May 29, 2022 at 7:37 PM Vinnie Falco via Boost < boost@lists.boost.org> wrote:

On Sun, May 29, 2022 at 7:30 PM Emil Dotchevski via Boost wrote:

...

std::bad_alloc is quite possible and it ought to be handled properly.

In almost 100% of cases, std::bad_alloc is thrown because the process has default memory restrictions via ulimit.

Also I made up that number.

At any rate it is no longer safe to assume that std::bad_alloc is the result of a failure to check for valid input; in a VM environment the system limits are often restricted.