🚀 go-pugleaf

> try and catch are the standard C++ method of managing exceptions.
>
> __try, __except, and __finally are related to the operating system
> exceptions.
>
> The two types of exceptions, and they way they are handled, are
> actually distinct.
>
> As OS exceptions are usually something that can be avoided by
> good coding, it is probably better to design your software so
> they don't occur in the first place.   If you feel you really must
> catch them, the recommended approach is to catch OS exceptions
> (using __except) and have the handler throw an appropriate C++
> exception.

You are absolutely right - I try usually to avoid such things by better
design / coding...
The problem occurs usually with third party components / OLE Automation
Servers I have to use...
They do whatever they do ok but sometime throw OS exceptions - I need to
catch these...
Otherwise my whole app behaves strange ( if I don't catch them )...

Even when using __except etc. with some exceptions it seems impossible to
catch them - esp. when they occur inside OLE Automation servers I use...
And this really makes my app reacting really strange when this happens...

Is there any way making sure that really all exceptions get caught ?

Yahia