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
June 2010

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

2010.06.17 15:39 "libtiff 4 API/ABI stability?", by Adam Goode
2010.06.17 16:21 "Re: libtiff 4 API/ABI stability?", by Edward Lam
2010.06.17 16:22 "Re: libtiff 4 API/ABI stability?", by Edward Lam
2010.06.17 16:38 "Re: libtiff 4 API/ABI stability?", by Adam Goode
2010.06.17 22:06 "Re: libtiff 4 API/ABI stability?", by Edward Lam
2010.06.18 00:13 "Re: libtiff 4 API/ABI stability?", by Adam Goode
2010.06.18 13:44 "Re: libtiff 4 API/ABI stability?", by Edward Lam
2010.06.18 17:46 "[PATCH] Build tif_win32.c on Windows except on Cygwin", by Adam Goode
2010.06.18 18:21 "Re: [PATCH] Build tif_win32.c on Windows except on Cygwin", by Bob Friesenhahn
2010.06.18 18:32 "Re: [PATCH] Build tif_win32.c on Windows except on Cygwin", by Adam Goode
2010.06.18 18:35 "Re: [PATCH] Build tif_win32.c on Windows except on Cygwin", by Adam Goode
2010.06.28 13:25 "Re: [PATCH] Build tif_win32.c on Windows except on Cygwin", by Edward Lam
2010.06.28 15:54 "Re: [PATCH] Build tif_win32.c on Windows except on Cygwin", by Bob Friesenhahn
2010.06.29 11:23 "Re: [PATCH] Build tif_win32.c on Windows except on Cygwin", by Andrey Kiselev
2010.06.29 13:46 "Re: [PATCH] Build tif_win32.c on Windows except on Cygwin", by Adam Goode
2010.06.17 16:28 "Re: libtiff 4 API/ABI stability?", by Bob Friesenhahn
2010.06.17 16:34 "Re: libtiff 4 API/ABI stability?", by Adam Goode
2010.06.17 16:55 "Re: libtiff 4 API/ABI stability?", by Bob Friesenhahn
2010.06.17 17:15 "Re: libtiff 4 API/ABI stability?", by Adam Goode
2010.06.17 18:04 "Re: libtiff 4 API/ABI stability?", by Olivier Paquet
2010.06.17 18:09 "Re: libtiff 4 API/ABI stability?", by Adam Goode
2010.06.17 18:47 "Re: libtiff 4 API/ABI stability?", by Bob Friesenhahn
2010.06.17 19:35 "Re: libtiff 4 API/ABI stability?", by Olivier Paquet
2010.06.18 00:33 "Re: libtiff 4 API/ABI stability?", by Adam Goode
2010.06.18 01:45 "Re: libtiff 4 API/ABI stability?", by Adam Goode
2010.06.18 01:54 "Re: libtiff 4 API/ABI stability?", by Olivier Paquet
2010.06.18 02:00 "Re: libtiff 4 API/ABI stability?", by Adam Goode
2010.06.18 13:32 "Re: libtiff 4 API/ABI stability?", by Edward Lam
2010.06.18 13:54 "Re: libtiff 4 API/ABI stability?", by Olivier Paquet
2010.06.18 02:36 "Re: libtiff 4 API/ABI stability?", by Bob Friesenhahn
2010.06.17 20:14 "Re: libtiff 4 API/ABI stability?", by Tom Lane
2010.06.17 20:35 "Re: libtiff 4 API/ABI stability?", by Bob Friesenhahn
2010.06.18 00:31 "Re: libtiff 4 API/ABI stability?", by Adam Goode

2010.06.17 16:34 "Re: libtiff 4 API/ABI stability?", by Adam Goode

On 06/17/2010 12:28 PM, Bob Friesenhahn wrote:
> On Thu, 17 Jun 2010, Adam Goode wrote:
> 
>> I was wondering if there are going to be any API or ABI incompatible
>> changes before the final release of libtiff 4.
>>
>> I know that it is still in beta, and may not be so close to a final
>> release, but I was hoping that I could count on programs compiled
>> against the beta would work without recompiling against the eventual
>> final release.
>>
>> Any thoughts on this?
> 
> The libtiff4 API and ABI should be pretty stable.  I am not aware of any
> API/ABI changes in this protracted beta cycle.  However, I would like to
> make a few global variables go away prior to the release, and removing
> them would technically change the ABI even though they are not intended
> to be used as part of the API.
> 

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.

We could identify this and put into a blocker bug for the release of
libtiff 4.


Adam