Re: exception handling anti-patterns in documentation

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

On Sun, May 29, 2022 at 7:25 PM Gavin Lambert via Boost <
boost_at_[hidden]> wrote:
>  Although it can still be argued that
> trying to make a too-large memory allocation is usually the result of a
> failure of input sanitisation (e.g. not checking data from input files),
> which is still a kind of coding bug.

This was the case some time ago but no longer -- in today's virtual
environments std::bad_alloc is quite possible and it ought to be handled
properly.