Thread

libjpeg is thread-safe as long as (a) you don't have multiple threads operating concurrently on the same jpeg object, and (b) your underlying C library (particularly malloc/free) is thread-safe. You can have multiple jpeg objects being manipulated concurrently by different threads.

I completely agree.

Bob Friesenhahn wrote:

> In this case, "underlying C library" would need to include

> setjmp/longjmp.

No, it wouldn't. Long jumps are not an actual part of LibJpeg, but merely one of the possible application-level encapsulation choices. Another option could be exceptions on some platforms, and at least on Windows platforms that seems to be a lot more common. In any case, it is outside of the LibJpeg library, a caller design choice, and a separate issue to consider.

Best regards,

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