AWARE SYSTEMS
TIFF and LibTiff Mail List Archive

Thread

2004.11.04 18:31 "[Tiff] is libtiff thread-safe?", by James Xu
2004.11.04 19:04 "Re: [Tiff] is libtiff thread-safe?", by Bob Friesenhahn
2004.11.04 19:09 "Re: [Tiff] is libtiff thread-safe?", by Chris Losinger
2004.11.05 09:19 "Re: [Tiff] is libtiff thread-safe?", by Joris
2004.11.04 23:51 "Re: [Tiff] is libtiff thread-safe?", by Joris
2004.11.05 14:38 "Re: [Tiff] is libtiff thread-safe?", by Bob Friesenhahn
[...]

2004.11.05 09:19 "Re: [Tiff] is libtiff thread-safe?", by Joris

> > I totally fail to see the connection between the lack of TIFF * parameter in the

> > callbacks on the one hand, and multi-threading on the other. The callbacks are

>
> In that case I will attempt to educate you.

How fortunate.

> If the functions provided a pointer to user context

> then the error information could simply be stored there, without any > need to use an OS-specific thread-API function to support

> thread-specific storage.

My point exactly. In other words, if the function were adequate... there would be not threading issue, nor any other issue of tracing back the error to its context, nor any other issue of storing the error description in the right place. In my view, that means the issue is not threading specific, not threading related.

Investigating the above quote the other way around now, the functions *not* providing a pointer to user context, the thread specific storage (threadvars or whatever) are *not* going to help you if the thread uses multiple TIFF *. It's still not possible in that case to trace back to user context.

In other words, threading is not related to this issue.

Joris Van Damme
info@awaresystems.be
http://www.awaresystems.be

Download your free TIFF tag viewer for windows here: http://www.awaresystems.be/imaging/tiff/astifftagviewer.html