From: Pavel Vozenilek (pavel_vozenilek_at_[hidden])
Date: 2004-10-27 22:10:10
"Stefan Seefeld" wrote:
> I'v recently run into a problem with 'catch(...)'
> on MSVC 7.1, where a segmentation fault resulted
> in a 'first-class exception' (!) that was caught
> by 'catch(...)' even though the stack wasn't
> unwound.
...
> I'd like to get your feedback on how to
> use it portably. Are my findings false?
>
No, it is behavior of MSVC by default.
This compiler has switch not to map
Win32 exceptions into C++ ones.
/Pavel