2010.11.30 20:08 "Re: [Tiff] Win32 ReadFile() / WriteFile() heads-up", by Toby Thain

On 30/11/10 2:58 PM, John Emmas wrote:

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?!?

The fact that the POSIX calls are there is what motivated my suggestion.

Of course, I realise that this is the kind of problem one only appreciates with the benefit of hindsight..! :-)

On 30 Nov 2010, at 19:24, Ian Ashley wrote:

>

> How about using TIFFClientOpen and providing your own callbacks for reading, writing, etc?

>

Okay, that's a good idea that didn't occur to me. I'm tempted to look into it - but.....

That's basically what I've done in the past, for other handle flavours.

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!

...that it breaks existing code isn't enough?

--Toby

> John
>
>
>

> _______________________________________________
> Tiff mailing list: Tiff@lists.maptools.org
> http://lists.maptools.org/mailman/listinfo/tiff
> http://www.remotesensing.org/libtiff/