-
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 23:16 "Re: [Tiff] compatibility patch", by Bob Friesenhahn
> > But what a problem with the standard tif_win32.c? Your new
> > tif_win32crt.c will be not portable anyway and specific for Windows.As stated in the patch, the problem with the standard tif_win32.c is that I can't make the following call from a windows application:
fp = fopen( "foo.tif", "rb")
TIFFFdOpen(fileno(fp),"r");This matters because my application only has a file pointer (FILE *fp) available when it calls libtiff. This is a very
It is worth mentioning that file pointers (FILE *fp) are only useful for accessing up to 2GB of data with 32-bit Windows. TIFF files can be as large as 4GB, and the future "Big TIFF" will allow terrabytes.
Due to the use of a common kernel DLL and the need for application compatibility across Windows versions, Windows does not offer a large-file compilation option like Unix does.
Bob
======================================
Bob Friesenhahn
bfriesen@simple.dallas.tx.us
http://www.simplesystems.org/users/bfriesen