Larry Gritz

> How do you think about to delete unnecessary null pointer checks at other source code places then? I'm all for it! My hesitation is specific to the dpx and...

> Would anybody dare to measure effects of questionable extra checks in the discussed source code? We measure all the time. But we don't need to measure in this case...

I don't have time to look into this, since it's a rare format that nobody will encounter in our primary user population and I don't recall any previous requests for...

Hey, at least we already have support for .sgi files! You never know when IRIX will come back into vogue.

First thing's first: do you really need Field3D support? If you aren't needing to read Field3D files as volumetric images, the easiest way out of this is just to build...

The first thing I would think of is, maybe you have two different Field3D installations, and it's somehow using the headers from one version but trying to link the other...

Hi, can you send the full log, not just a clip of the error messages? Also, what platform and compiler?

Hi, please try this to get the whole log, including the config step: # from the main oiio directory: make nuke all VERBOSE=1 | tee build.log

I can't help but notice that in the first example of error messages, you were expecting Field3D 1.7 which had clearly been built against OpenEXR 2.3 and using std::string parameters:...

I think you're trying to link against a Field3D that was build with a different OpenEXR and maybe also a different C++ ABI compatibility (not using the same string type).