🚀 go-pugleaf

Hi :-)

I asked the following on language.cpp and since it deals with OS exceptions
+ C++ exceptions I post here too to get the other half :-)

AFAIK the C++ standard says that all exceptions shouldn't evolve out out the
following code block :

{
try {
      // here comes some code... any exception should be absorbed by the
following catch(...) ?!?

     }
catch(...)
     {
     };
}


BUT I experienced that with some third party components / Win32 API calls
exceptions occur which just aren't catched by the above code.
Then I tried some options and came up with the following code :

{
try {
    try {
        try {
             // here comes some code...

            }
        __except ( EXCEPTION_EXECUTE_HANDLER )
            {
            };
        }
    catch (...)
        {
        };
    }
__finally
    {
    };
}

This code absorbs now all exceptions ( C++ ones AND Win32 ones AND whatever
comes from third party components like DOA ). It works usually good but
shows sometimes strange behaviour ( like just freezing the app OR having
some exceptions i.e. from ActiveX interfaces still come up in a dialog... ).

The purpose of the above code is to make sure that all exceptions are
handled in a way that my clean up code following the block you see always
gets executed...

Then I read that mixing C and C++ try / catch /__except / __finally is
somehow not recommended and buggy in BCB 5 and 6...

Could someone be so kind to provide me with some details on this ?

Thanks in advance

Yahia