Re: Are throwing default constructors bad style, and if so, why?
on Tue Oct 21 2008, Marsh Ray <marsh527-AT-gmail.com> wrote:
{ Accepted as a follow-up. Posters are advised that further environment-
specific discussions are better directed to other groups. -mod }
Well, understood, but it's a question that deserves an answer.
On Oct 16, 10:14 pm, David Abrahams <d...@boostpro.com> wrote:
Then it's a bad platform, because unless something has changed in the
past few years, all Windows 32-bit compilers still use a
setjmp/longjmp-like implementation of EH so they can interoperate with
"structured exception handling." It's usually not a particularly good
idea to interoperate that way, but that's the norm on 32-bit Windows.
Metrowerks, when they still existed, used to offer an option to do EH
the fast way or the interoperable way, but they're long gone now :(.
...
Got any suggestions? For now at least, 32-bit Windows is still an
important platform to support.
Have you looked into MSVC's /EHsc compiler setting instead of /EHa?
It seems to allow the compiler to disregard any exceptions from non-C+
+ code, so 'catch (...)' no longer catches general SEH exceptions.
Yes of course I am aware of that. Unfortunately on 32-bit windows it
still uses the "dumb, slow" implementation, to preserve ABI
compatibility. 64-bit is a different matter.
--
Dave Abrahams
BoostPro Computing
http://www.boostpro.com
[ See http://www.gotw.ca/resources/clcm.htm for info about ]
[ comp.lang.c++.moderated. First time posters: Do this! ]