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 2010

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

2010.11.30 19:15 "Win32 ReadFile() / WriteFile() heads-up", by John Emmas
2010.11.30 19:26 "Re: Win32 ReadFile() / WriteFile() heads-up", by Toby Thain
2010.11.30 19:58 "Re: Win32 ReadFile() / WriteFile() heads-up", by John Emmas
2010.11.30 20:08 "Re: Win32 ReadFile() / WriteFile() heads-up", by Toby Thain
2010.11.30 20:12 "Re: Win32 ReadFile() / WriteFile() heads-up", by Frank Warmerdam
2010.12.01 17:40 "Re: Win32 ReadFile() / WriteFile() heads-up", by John Emmas
2010.12.05 18:36 "Re: Win32 ReadFile() / WriteFile() heads-up", by Edward Lam
2010.11.30 19:43 "Re: Win32 ReadFile() / WriteFile() heads-up", by Kevin Myers
2010.12.01 05:15 "Re: Win32 ReadFile() / WriteFile() heads-up", by Bob Friesenhahn
2010.12.01 08:45 "Re: Win32 ReadFile() / WriteFile() heads-up", by John Emmas
2010.12.01 06:35 "Re: Tiff Digest, Vol 79, Issue 1 - Win32 ReadFile() / WriteFile() heads-up (John Emmas)", by David J Taylor
2010.12.01 12:37 "Re: Win32 ReadFile() / WriteFile() heads-up", by Phil Harvey
2010.12.05 18:05 "Re: Win32 ReadFile() / WriteFile() heads-up", by Edward Lam

2010.11.30 20:12 "Re: Win32 ReadFile() / WriteFile() heads-up", by Frank Warmerdam

John Emmas wrote:
> 
> On 30 Nov 2010, at 19:26, Toby Thain wrote:
> 
>>
>> Can't the existing tif_unix entry points be used, if the application
>> wants to use POSIX file handles?
>>
> I didn't have time to try that today but I figure it would probably work 
> fine.  It's not as intuitive though as using tif_win32.  You'd have to 
> know up front that the unix entry points apply if you wish to use 
> libTIFF in conjunction with a POSIX based, 3rd party library.  Most devs 
> probably wouldn't assume that and would most likely just use the 
> supplied win32 interfaces (I did).  Especially since the POSIX style 
> function calls are already present in Win32?!?

John,

This is certainly not the only unobvious aspect of libtiff.  But
the intension if if you want to use the POSIX style API you should
use tif_unix.c.  It might make sense to rename it tif_posix.c.

> On 30 Nov 2010, at 19:43, Kevin Myers wrote:
> 
>> I haven't looked into this very much *at all*, so what I am about to say 
>> could easily be *very* wrong.  That being said, wouldn't changing 
>> libtiff to 
>> use read() and write() break large file handling (greater than 4GB) under 
>> Win32?
> 
> Hmmm....  okay, that's a pretty good reason if it's true!

It has certainly been my assumption that the posix api implementation is
generally only suitable for 32bit file sizes though that might be old
information or due to my misuse of them in the past.  >2GB files might
also not matter much for your application.

Best regards,
-- 
---------------------------------------+--------------------------------------
I set the clouds in motion - turn up   | Frank Warmerdam, warmerdam@pobox.com
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush    | Geospatial Programmer for Rent