AWARE SYSTEMS
TIFF and LibTiff Mail List Archive

Thread

2004.06.28 13:18 "[Tiff] Throwing C++ exceptions from custom error handler", by Eric Fieleke
2004.06.29 14:22 "RE: [Tiff] Throwing C++ exceptions from custom error handler", by Eric Fieleke
2004.07.01 14:04 "RE: [Tiff] Throwing C++ exceptions from custom error handler", by Eric Fieleke
2004.07.03 10:30 "Re: [Tiff] Throwing C++ exceptions from custom error handler", by Andrey Kiselev

2004.07.01 14:04 "RE: [Tiff] Throwing C++ exceptions from custom error handler", by Eric Fieleke

I also found a case where a TIFF method can fail but the error handler does not get called. In this case the warning handler did get called (TIFFVSetField returned 0, and I got a warning something like "cannot pass by value to _TIFFVSetField").

This behavior seems inconsistent to me. If a method is going to fail, I'd expect the error handler to get called. If it is going to succeed, I'd expect the error handler to NOT get called (warnings would of course always be OK). tifflib does not always behave this way, however.

Just something to consider.