Boost logo

Boost Users :

From: Ben Hutchings (ben.hutchings_at_[hidden])
Date: 2004-08-25 07:31:30

Peter Dimov <pdimov_at_[hidden]> wrote:
> Ben Hutchings wrote:
> > Peter Dimov <pdimov_at_[hidden]> wrote:
> >> 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.
> >
> > This is an known and unresolved issue:
> >
> "The copy constructors of all exception-derived classes already have
> a no throw spec. Reference 18.6.1, 19.1 and 15.4/13."

"As they stand, the copy constructors might fail via a call to
unexpected. I think what is intended here is that the copy
constructors can't fail."

(Is it really necessary for us to quote the referenced text at each
other? This is silly.)

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