AWARE [SYSTEMS] Imaging expertise for the Delphi developer
AWare Systems, Imaging expertise for the Delphi developer, Home TIFF and LibTiff Mailing List Archive

LibTiff Mailing List

TIFF and LibTiff Mailing List Archive
January 2000

Previous Thread
Next Thread

Previous by Thread
Next by Thread

Previous by Date
Next by Date

Contact

The TIFF Mailing List Homepage
This list is run by Frank Warmerdam
Archive maintained by AWare Systems



Valid HTML 4.01!



Thread

2000.01.30 01:02 "libtiff in a M$ Windows Visual C++ 5.0 DLL for Borland Delphi 3,4,5", by Joris Van Damme
2000.01.31 14:46 "Re: libtiff in a M$ Windows Visual C++ 5.0 DLL for Borland Delphi 3,4,5", by Bruce Cameron
2000.01.31 15:02 "Re: libtiff in a M$ Windows Visual C++ 5.0 DLL for Borland Delphi 3,4,5", by Frank Warmerdam
2000.01.31 15:05 "Re: libtiff in a M$ Windows Visual C++ 5.0 DLL for Borland Delphi 3,4,5", by Scott Wagner
2000.01.31 18:29 "Re: Threadsafe MSVC implementation of LibTiff", by Scott Wagner
2000.02.05 01:06 "Re: threadsafety of libtiff 3.5.4?", by Frank Warmerdam

2000.01.31 18:29 "Re: Threadsafe MSVC implementation of LibTiff", by Scott Wagner

The build of libtiff which I use is built from source by me - not Frank
Warmerdam's build.  Mine is a threadsafe DLL, and I call it from
multithreaded applications.  My experience is that (at least with my
Borland compiler) the default C runtime library code selected is the more
compact single-thread version; I have to select the multi-threaded CRTL as
an option.  This is probably true of VC++ as well.

Frank, can you comment on this?

At 11:58 01/31/2000 -0600, you wrote:
>When you say 'including its DLL incarnation' does this mean that the
>basic '.lib' library is reentrant??
>
>> LibTiff (including its Windows DLL incarnation) is almost(!) reentrant.
>> That is, the only pieces which are non-reentrant are the pieces which set
>> up the warning and error handlers.  For most uses, this is OK - set up your
>> warning and error handlers at initialization; then you can handle multiple
>> images with multiple TIFF handles without collisions.


/*********************************************************************
* Scott Wagner  (swagner@itek.com)    NOTICE: My personal information,
* Staff Engineer                      including my E-mail address, may
* Itek Graphix                        not be sold, distributed, or made
* Rochester, NY USA                   public without my consent.
*********************************************************************/