Boost logo

Boost Users :

From: Thorsten Ottosen (nesotto_at_[hidden])
Date: 2004-08-26 11:20:37

"David Abrahams" <dave_at_[hidden]> wrote in message
| "Peter Dimov" <pdimov_at_[hidden]> writes:
| > Victor A. Wagner Jr. wrote:
| >> OK, blunt point.
| >> the standard is (insert favorite expletive or "in error") if it
| >> allows use of std::runtime_error to terminate the program due to low
| >> memory situations (run out of memory (due to copying) during stack
| >> unwinding).
| >
| > It does not allow such a thing.
| No? It seemed to me that it does, for perversely low QOI
| implementations.

hm...funny. I talked with Matt Austern and Peter Becker about this in Sydney. They made me believe
that if the copy-constrctor of a string throws in this line

throw std::run_time_error( "foo" );

then it wouldn't call terminate, but instead throw the wrong exception, namely (probably) a bad_alloc.

Is that a misunderstanding?



Boost-users list run by williamkempf at, kalb at, bjorn.karlsson at, gregod at, wekempf at