| AWARE [SYSTEMS] | Imaging expertise for the Delphi developer | |||||||
![]() |
TIFF and LibTiff Mailing List Archive | |||||||
LibTiff Mailing List
TIFF and LibTiff Mailing List Archive Contact
The TIFF Mailing List Homepage |
Thread2010.06.17 16:55 "Re: libtiff 4 API/ABI stability?", by Bob FriesenhahnOn Thu, 17 Jun 2010, Adam Goode wrote: > > Yeah, getting rid of globals is a great thing to do. I started to look > at this some months ago: which globals are you interested in > eliminating? I had an idea for introducing new API calls that don't use > various globals so that new code could be safe, while old code could > still work as before. There may be more, but the ones I noticed are related to the error/warning handlers. These handlers are not thread safe. There are also some non-const static variables used in the library. It would be good to decide if libtiff should be thread safe. If so, everything needs to be naturally re-entrant, or support for locks needs to be added in a few places. Bob -- Bob Friesenhahn bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/ GraphicsMagick Maintainer, http://www.GraphicsMagick.org/ |
|||||||