AWARE SYSTEMS
TIFF and LibTiff Mail List Archive

Thread

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.23 23:16 "Re: [Tiff] compatibility patch", by Bob Friesenhahn
2004.11.24 06:33 "Re: [Tiff] compatibility patch", by Andrey Kiselev
2004.11.24 19:39 "Re: [Tiff] compatibility patch", by Jeff Breidenbach
2004.11.24 20:37 "Re: [Tiff] compatibility patch", by Andrey Kiselev
2004.11.24 20:58 "Re: [Tiff] compatibility patch", by Edward Lam
2004.11.24 21:12 "Re: [Tiff] compatibility patch", by Andrey Kiselev
2004.11.24 14:45 "Re: [Tiff] compatibility patch", by Frank Warmerdam
2004.11.24 18:37 "Re: [Tiff] compatibility patch", by Andrey Kiselev
2004.11.28 14:46 "Re: [Tiff] compatibility patch", by Andrey Kiselev

2004.11.23 20:34 "Re: [Tiff] compatibility patch", by Andrey Kiselev

We submitted this patch a few years ago, didn't hear much. What do people think now? This makes file I/O interfaces in libtiff/win32 and libtiff/*nix compatible, which is handy when writing cross platform applications.

I can add tif_win32crt.c to the distribution with the special option in nmake.opt file, so user can select what I/O interface to use.

But what a problem with the standard tif_win32.c? Your new tif_win32crt.c will be not portable anyway and specific for Windows.

Andrey

Andrey V. Kiselev
Home phone: +7 812 5970603 ICQ# 26871517