|
Boost : |
From: Hillel Y. Sims (hsims_at_[hidden])
Date: 2002-09-30 10:24:06
"David Abrahams" <dave_at_[hidden]> wrote in message
news:060201c26675$e423e680$6501a8c0_at_boostconsulting.com...
>
> > especially if you are trying to
> > write safe portable code (besides, they could be implemented as
> "really-C++"
> > exceptions on a given platform too).
>
> In that case, try/catch would be fine.
>
Agreed, if they have accessible C++ typenames. However, in the case that you
cannot access the exception by its C++ typename from your user/library code
(because the OS keeps it hidden for some reason; this would simulate
essentially the same effect as non-C++ SEH-exceptions), then you'd only be
able to use catch(...).
hys
-- Hillel Y. Sims FactSet Research Systems hsims AT factset.com
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk