From: David Abrahams (dave_at_[hidden])
Date: 2006-03-29 09:57:35
"Fernando Cacciola" <fernando_cacciola_at_[hidden]> writes:
> The default policy is to use the "internal range checking" logic, which, if
> the source or target types are UDT, means no range checking at all.
>
> But you can, however, create and pass your own range checking policy.
> Is just that you can't simply use numeric_cast<> then.
That's rather a shame. It would be better for generic code if the
checking policy could be specified non-intrusively, e.g. via some
traits.
-- Dave Abrahams Boost Consulting www.boost-consulting.com