> I'm afraid that it could be true that only *MY* C++ bridge is making > trouble. It could be a problem with my compiler, because I use different > versions of MS VisualStudio on the same computer and the comment on > cppu::getCaughtException() tells that there could be problems with different > versions of msvcrt.dll.
The msvc bridge needs to figure out the (rethrown) exception using internals of the msvcrt. The internal offsets are pinned at compile time, i.e. via #if _MSC_VER ... for msvcrt.dll, msvcr70.dll and msvcr71.dll. As OOo comes with the matching msvcr, there is no problem, as stated in the documentation of getCaughtException() (which is currently the only function using the bridges' "get the rethrown exception" feature). Supporting OOo being built with Visual Studio 8, e.g. the Express compiler, this will require adoptions in the msvc bridge, supporting that msvcr. getCaughtException() is good for OOo internal development and if you make sure to only use one msvcrt, i.e. the one the SDK links against (currently msvcr70.dll). Free SDK use is *not* recommended. HTH, ~Daniel --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
