Re: [Boost-users] Re: Guidelines for effective exception usage

From: Victor A. Wagner Jr. (vawjr_at_[hidden])
Date: 2004-08-24 09:21:08

At Tuesday 2004-08-24 00:39, you wrote:
>"Victor A. Wagner Jr." <vawjr_at_[hidden]> writes:
>
> > At Monday 2004-08-23 13:55, you wrote:
> >>Jeff Holle <jeff.holle_at_[hidden]> writes:
> >>
> >> > My two cents of the referenced html page.
> >> >
> >> > Not placing attributes like string into an exception class only makes
> >> > sense if the exception being thrown has
> >> > something to do with a memory starvation situation.
> >> >
> >> > For a lot of exception types that I can think of this is not the case.
> >> >
> >> > As an example of this std::runtime_error often has a string attribute
> >> > and this is perfectly fine.
> >>
> >>No it is not.  Even if you aren't throwing due to memory starvation,
> >>you could run out of memory during unwinding, when the exception is
> >>copied.  That leads you directly to terminate().  Do not pass Go; do
> >>not collect $200.
> >
> > why would unwinding copy the exception?
>
>Because the language specification says it can.

you _can_ paint your face with green and red polka dots also.
doesn't mean the rest of us won't or shouldn't ridicule those who do.

Not to put TOO fine a point on it, but the entire raison d’ętre of creating 
a language and libraries is to make is _easy_ for the user to write things.

>--
>Dave Abrahams
>Boost Consulting
>http://www.boost-consulting.com

Victor A. Wagner Jr.      http://rudbek.com
The five most dangerous words in the English language:
               "There oughta be a law"