30 May
2022
30 May
'22
2:29 a.m.
On Sun, May 29, 2022 at 7:25 PM Gavin Lambert via Boost < boost@lists.boost.org> 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.