Re: [jamboost] feature eh-model question

From: Rene Rivera (grafik666_at_[hidden])
Date: 2002-08-27 10:40:45

[2002-08-27] Patrick Frants wrote:

>Hi,
>
>I found the eh-model feature and it was apparently added for the Metroworks 
>compiler. 
>
>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.

This was put in to handle the configuration of Metorwerks (and any other
compiler that can similate MSVC) to act like MSVC. But currently only the
metrowerks toolset implements this. And yes it seems a bit strange to add
msvc-sync/async as we try to put only cross-toolset options in the global
features.

So yes, I would suggest you put a feature in your toolset to select the
sync/async exceptions.

-- grafik - Don't Assume Anything
-- rrivera_at_[hidden] - grafik_at_[hidden]
-- 102708583_at_icq - Grafik666_at_AIM - Grafik_at_[hidden]