Re: [Openexr-devel] Exceptions in the DLL

[Paul Nolan]

Hi Paul,
 
> I took a quick look at the C interfaces (ImfCRgbaFile.cpp) and it seems 
> to catch any exceptions thrown in exported functions, and return error 
> codes instead.  ImfOpenInputFile, for example, is surrounded by a 
> try/catch block.  Of course, it's only catching std::exceptions, and I 
> seem to remember that the Microsoft compiler likes to throw other kinds 
> of exceptions (often in violation of the C++ standard), so maybe that's 
> the problem.  If you can find a case where the C interfaces are 
> propagating exceptions back from the C library, that's definitely a bug 
> that should be fixed.

It does look like that could be the case, or it could also be that you 
can't throw any exceptions full stop when the compiler versions don't 
match, I don't know how that works.

> Of course, none of this solves your problem.  You're right, we should 
> ship our precompiled libraries with documentation describing exactly 
> what development system was used to buid them, and a note explaining 
> that those who wish to use a different system should recompile the 
> libraries.

That would be good, especially with VS2005 coming out, more people are 
likely to run into this type of problem in the future.

Thanks,

Paul Nolan, CEO Idruna Software Inc.
http://www.idruna.com