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
November 2004

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

2004.11.17 18:13 "compatibility patch", by Jeff Breidenbach
2004.11.23 20:34 "Re: compatibility patch", by Andrey Kiselev
2004.11.23 20:58 "Re: compatibility patch", by Bob Friesenhahn
2004.11.23 21:24 "Re: compatibility patch", by Edward Lam
2004.11.23 21:28 "Re: compatibility patch", by Edward Lam
2004.11.23 21:51 "Re: compatibility patch", by Bob Friesenhahn
2004.11.23 22:04 "Re: compatibility patch", by Edward Lam
2004.11.23 22:33 "Re: compatibility patch", by Jeff Breidenbach
2004.11.23 23:16 "Re: compatibility patch", by Bob Friesenhahn
2004.11.24 06:33 "Re: compatibility patch", by Andrey Kiselev
2004.11.24 19:39 "Re: compatibility patch", by Jeff Breidenbach
2004.11.24 20:37 "Re: compatibility patch", by Andrey Kiselev
2004.11.24 20:58 "Re: compatibility patch", by Edward Lam
2004.11.24 21:12 "Re: compatibility patch", by Andrey Kiselev
2004.11.24 14:45 "Re: compatibility patch", by Frank Warmerdam
2004.11.24 18:37 "Re: compatibility patch", by Andrey Kiselev
2004.11.28 14:46 "Re: compatibility patch", by Andrey Kiselev

2004.11.23 22:33 "Re: compatibility patch", by Jeff Breidenbach

> > 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 
clean and convenient interface. It works great with libtiff on
*nix. With the patch, it also works for Win32.

> So somehow combining the best of both files. I think we want:
> - 4GB files
> - memory-mapped files
> - the more user-friendly Win32 error handler from tif_win32.c

Let's put "consistant calling interfaces between Win32 and Unix"
on the list as well. 

Cheers,
Jeff


-- 
Jeff Breidenbach <jbreiden@parc.com>
Palo Alto Research Center (PARC)