2004.11.17 18:13 "[Tiff] compatibility patch", by Jeff Breidenbach
-
2004.11.23 20:34 "Re: [Tiff] compatibility patch", by Andrey Kiselev
-
2004.11.23 20:58 "Re: [Tiff] compatibility patch", by Bob Friesenhahn
-
2004.11.23 21:24 "Re: [Tiff] compatibility patch", by Edward Lam
- 2004.11.23 21:28 "Re: [Tiff] compatibility patch", by Edward Lam
-
2004.11.23 21:51 "Re: [Tiff] compatibility patch", by Bob Friesenhahn
-
2004.11.23 22:04 "Re: [Tiff] compatibility patch", by Edward Lam
- 2004.11.23 22:33 "Re: [Tiff] compatibility patch", by Jeff Breidenbach
- 2004.11.28 14:46 "Re: [Tiff] compatibility patch", by Andrey Kiselev
-
2004.11.23 22:04 "Re: [Tiff] compatibility patch", by Edward Lam
-
2004.11.23 21:24 "Re: [Tiff] compatibility patch", by Edward Lam
-
2004.11.23 20:58 "Re: [Tiff] compatibility patch", by Bob Friesenhahn
2004.11.23 21:24 "Re: [Tiff] compatibility patch", by Edward Lam
Hi Bob,
If you look at the MSVCRT source, they are basically just wrappers around the Win32 functions used in tif_win32.c anyhow. I would suggest that you take a look yourself at tif_win32.c. I think that tif_win32.c might also be more 64-bit friendly. If we have 4GB issues, they will likely lie more with the fact that t_sizet is defined as int32 instead of uint32.
It seems to me that the advantage with tif_win32crt.c is that it has #ifdef's to allow it to be compiled on Unix environments. But if that's the case, then just use a platform-specific driver.
Regards,
-Edward