Re: exception handling anti-patterns in documentation

From: Emil Dotchevski (emildotchevski_at_[hidden])
Date: 2022-05-30 02:48:16

On Sun, May 29, 2022 at 7:37 PM Vinnie Falco via Boost <
boost_at_[hidden]> wrote:
>
> On Sun, May 29, 2022 at 7:30 PM Emil Dotchevski via Boost
> <boost_at_[hidden]> 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.