- 2010.06.17 16:21 "Re: [Tiff] libtiff 4 API/ABI stability?", by Edward Lam
-
2010.06.17 16:28 "Re: [Tiff] libtiff 4 API/ABI stability?", by Bob Friesenhahn
-
2010.06.17 16:34 "Re: [Tiff] libtiff 4 API/ABI stability?", by Adam Goode
-
2010.06.17 16:55 "Re: [Tiff] libtiff 4 API/ABI stability?", by Bob Friesenhahn
-
2010.06.17 17:15 "Re: [Tiff] libtiff 4 API/ABI stability?", by Adam Goode
-
2010.06.17 18:04 "Re: [Tiff] libtiff 4 API/ABI stability?", by Olivier Paquet
-
2010.06.17 18:09 "Re: [Tiff] libtiff 4 API/ABI stability?", by Adam Goode
-
2010.06.17 18:47 "Re: [Tiff] libtiff 4 API/ABI stability?", by Bob Friesenhahn
-
2010.06.17 19:35 "Re: [Tiff] libtiff 4 API/ABI stability?", by Olivier Paquet
-
2010.06.18 00:33 "Re: [Tiff] libtiff 4 API/ABI stability?", by Adam Goode
- 2010.06.18 01:45 "Re: [Tiff] libtiff 4 API/ABI stability?", by Adam Goode
-
2010.06.18 00:33 "Re: [Tiff] libtiff 4 API/ABI stability?", by Adam Goode
- 2010.06.17 20:14 "Re: [Tiff] libtiff 4 API/ABI stability?", by Tom Lane
- 2010.06.18 00:31 "Re: [Tiff] libtiff 4 API/ABI stability?", by Adam Goode
-
2010.06.17 19:35 "Re: [Tiff] libtiff 4 API/ABI stability?", by Olivier Paquet
-
2010.06.17 18:47 "Re: [Tiff] libtiff 4 API/ABI stability?", by Bob Friesenhahn
-
2010.06.17 18:09 "Re: [Tiff] libtiff 4 API/ABI stability?", by Adam Goode
-
2010.06.17 18:04 "Re: [Tiff] libtiff 4 API/ABI stability?", by Olivier Paquet
-
2010.06.17 17:15 "Re: [Tiff] libtiff 4 API/ABI stability?", by Adam Goode
-
2010.06.17 16:55 "Re: [Tiff] libtiff 4 API/ABI stability?", by Bob Friesenhahn
-
2010.06.17 16:34 "Re: [Tiff] libtiff 4 API/ABI stability?", by Adam Goode
2010.06.17 16:38 "Re: [Tiff] libtiff 4 API/ABI stability?", by Adam Goode
On 06/17/2010 12:21 PM, Edward Lam wrote:
I was wondering if there are going to be any API or ABI incompatible changes before the final release of libtiff 4.
If you care about Windows, bug 1941 [1] is still open. If it gets fixed, then the behaviour for the following functions will change on Windows: TIFFFdOpen(), TIFFFileno(), TIFFSetFileno(), TIFFClientdata(), TIFFSetClientdata().
I am not quite as concerned with Windows behavior as Unix, since shipping dependent DLLs is the norm on Windows, but this could change if CoApp[1] becomes popular (as I hope it does).
I think this should be fixed before libtiff 4. Is anyone interested in making a release blocker bug in bugzilla? We could add this bug to it.
Also, I wonder why the tif_win32.c file isn't enabled by default on Windows. With tif_unix.c, the file interface is limited to 2GB on Windows. tif_win32.c is needed for large file access (the whole point of libtiff 4?).
Adam
[1]: http://coapp.org/