2016.07.05 19:52 "Re: [Tiff] Proposed API improvements", by Olivier Paquet
2016-07-05 13:18 GMT-04:00 Bob Friesenhahn <email@example.com>:
Binding the error handler to a TIFF handle will fix the issue except for the case where there is not yet a TIFF handle.
Some grepping shows the codec registration functions are the only ones to have this problem. Everything else appears to either take a handle or not yet produce any error messages. It is still a valid design concern but I can't think of any nice solution. The least ugly one appears to be registering codecs to an open TIFF handle instead of globally. This is required for thread safety or multiple users in a single thread anyway.