2017.07.05 12:12 "Re: [Tiff] A bug in libtiff error/warning handling", by Edward Lam

On 7/4/2017 2:38 PM, Bob Friesenhahn wrote:

This would not work for the common case of reporting an error when there is no TIFF handle. There would need to be additional parameters added for the functions which open a a TIFF.

If OS thread APIs can be used, then there is the option to use thread specific data without any API change, but a possible added library dependency.

Just thinking out loud here. If there was some way to get the client code to provide a callback that returned a thread specific id, then libtiff could use that as a key into a thread-specific data structure (eg. hash table). Then there would not require an additional library dependency other than what the client code decides that it wants to do. If no such function is provided, then we can always just go back to the default current behaviour of not being thread-safe(?).

-Edward