|
Boost : |
From: Vinnie Falco (vinnie.falco_at_[hidden])
Date: 2022-05-30 02:37:15
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.
Thanks
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk