From: Patrick Frants (gclbb-jamboost_at_[hidden])
Date: 2002-08-27 03:17:08
I found the eh-model feature and it was apparently added for the Metroworks
feature eh-model : default fast msvc ; # metrowerks only
One of the possible values is now msvc, but the msvc compiler has at least
two different exception handling models (sync and async). The problem is
that this qualification is different from default <-> fast, therefore
splitting the msvc value into sync and async (or msvc-sync, msvc-async) is
a bit strange, but it gives the possibility of choosing the exception
handling model. Of course I could also implement it in my own toolset.
The MSVC 6 documentation for the /EH flag:
This option specifies the model of exception handling to be used by the
Use /EHs to specify the synchronous exception handling model.
Use /EHa to specify the asynchronous exception handling model.
The /EHc option requires that /EHs, /EHa, or /GX is specified. It tells the
compiler to assume that extern C functions never throw an exception.
The option can be cleared by the symbol -. For example: /EHsc- is
interpreted as /EHs /EHc- , and is equivalent to /EHs.
-- Patrick Frants Senior Software Engineer Quintiq mailto:patrick_at_[hidden] www.quintiq.com
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk