[boost] Re: bad_numeric_cast is missing throw() specifier

From: Dave Abrahams (abrahams_at_[hidden])
Date: 1999-10-11 19:55:54

> This will result in no compile-time checking
> The run-time behavior is not advantageous
> Few compilers can use it for optimization
> Even among those that do, it will usually only result in a small reduction
> in executable size
> Many compilers will use it for pessimization, resulting in a large cost in
> executable size and often, speed.
>
>      Yes, this is all true when introducing new classes into a system.
>      However, because throw specs must be covariant wrt inheritance and
>      overriding virtual functions, bad_numeric_cast is required in this
>      case -- it is an error for it not to be (hence my comment about humans
>      having the edge on compilers :->).

Only humans that pay attention (oops!)
-Dave