Return-Path: <tiff-bounces@remotesensing.org>
Received: from inav012.isp.belgacom.be (inav012.isp.belgacom.be [195.238.3.55])
        by mailst035.isp.belgacom.be (8.12.11/8.12.11/Skynet-MAILSTORE-2.14) with ESMTP id iANLPYBb012604
        for <joris.at.lebbeke@skynet.be>; Tue, 23 Nov 2004 22:25:36 +0100
        (envelope-from <tiff-bounces@remotesensing.org>)
Received: from inas014.isp.belgacom.be (localhost [127.0.0.1])
        by inav012.isp.belgacom.be (8.12.11/8.12.11/Skynet-IN-AV-3.00) with ESMTP id iANLPJap011626
        for <joris.at.lebbeke@skynet.be>; Tue, 23 Nov 2004 22:25:19 +0100
        (envelope-from <tiff-bounces@remotesensing.org>)
Received: from inmx005.isp.belgacom.be (inmx005.isp.belgacom.be [195.238.3.148])
        by inas014.isp.belgacom.be (8.12.11/8.12.11/Skynet-IN-AS-2.03) with ESMTP id iANLP6Wf025530
        for <joris.at.lebbeke@skynet.be>; Tue, 23 Nov 2004 22:25:08 +0100
        (envelope-from <tiff-bounces@remotesensing.org>)
Received: from xserve.flids.com (adsl-065-083-169-202.sip.mco.bellsouth.net [65.83.169.202])
        by inmx005.isp.belgacom.be (8.12.11/8.12.11/Skynet-IN-2.32) with ESMTP id iANLP0oa027010
        for <joris.at.lebbeke@skynet.be>; Tue, 23 Nov 2004 22:25:02 +0100
        (envelope-from <tiff-bounces@remotesensing.org>)
Received: from adsl-065-083-169-202.sip.mco.bellsouth.net (localhost [127.0.0.1])
	by xserve.flids.com (Postfix) with ESMTP
	id 30C0B49CC9D; Tue, 23 Nov 2004 16:24:46 -0500 (EST)
X-Original-To: tiff@remotesensing.org
Delivered-To: tiff@remotesensing.org
Received: from mail.sidefx.com (tor149-99-58-193.dedicated.sprintdsl.ca
	[149.99.58.193])
	by xserve.flids.com (Postfix) with ESMTP id 89A8049CC7A
	for <tiff@remotesensing.org>; Tue, 23 Nov 2004 16:24:41 -0500 (EST)
Received: from [192.168.237.144] (crete.ithaca.sidefx.com[192.168.237.144])
	by mail.sidefx.com (Smail-3.2.0.111 2000-Feb-17 #5; 2004-May-20)
	(2568 bytes) via sendmail with /P:esmtp/R:inet_hosts/T:smtp
	id <m1CWi9B-004coRC@mail.sidefx.com> (sender <edward@sidefx.com>)
	for <tiff@remotesensing.org>; Tue, 23 Nov 2004 16:24:25 -0500 (EST)
Message-ID: <41A3AA8E.5090400@sidefx.com>
Date: Tue, 23 Nov 2004 16:24:30 -0500
From: Edward Lam <edward@sidefx.com>
User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Bob Friesenhahn <bfriesen@simple.dallas.tx.us>
Subject: Re: [Tiff] compatibility patch
References: <1100715200.10008.26.camel@rode.parc.com>	<20041123203437.GA12262@ak4719.spb.edu>
	<Pine.SOC.4.60.0411231455110.9670@blade.simplesystems.org>
In-Reply-To: <Pine.SOC.4.60.0411231455110.9670@blade.simplesystems.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: tiff@remotesensing.org
X-BeenThere: tiff@remotesensing.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: TIFF and libtiff discussion  <tiff.remotesensing.org>
List-Unsubscribe: <http://xserve.flids.com/mailman/listinfo/tiff>,
	<mailto:tiff-request@remotesensing.org?subject=unsubscribe>
List-Archive: <http://xserve.flids.com/pipermail/tiff>
List-Post: <mailto:tiff@remotesensing.org>
List-Help: <mailto:tiff-request@remotesensing.org?subject=help>
List-Subscribe: <http://xserve.flids.com/mailman/listinfo/tiff>,
	<mailto:tiff-request@remotesensing.org?subject=subscribe>
Sender: tiff-bounces@remotesensing.org
Errors-To: tiff-bounces@remotesensing.org
X-UIDL: 6565127bf05e4b1ebf82d9f16865e10e

Hi Bob,

If you look at the MSVCRT source, they are basically just wrappers around the 
Win32 functions used in tif_win32.c anyhow. I would suggest that you take a look 
yourself at tif_win32.c. I think that tif_win32.c might also be more 64-bit 
friendly. If we have 4GB issues, they will likely lie more with the fact that 
t_sizet is defined as int32 instead of uint32.

It seems to me that the advantage with tif_win32crt.c is that it has #ifdef's to 
allow it to be compiled on Unix environments. But if that's the case, then just 
use a platform-specific driver.

Regards,
-Edward

Bob Friesenhahn wrote:
> On Tue, 23 Nov 2004, Andrey Kiselev wrote:
> 
>> On Wed, Nov 17, 2004 at 10:13:20AM -0800, Jeff Breidenbach wrote:
>>
>>> 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.
> 
> 
> Does the alternative implementation support 4GB files?  Large file 
> support is often an issue under Windows.
> 
> Bob
> ======================================
> Bob Friesenhahn
> bfriesen@simple.dallas.tx.us
> http://www.simplesystems.org/users/bfriesen
> _______________________________________________
> Tiff mailing list
> Tiff@remotesensing.org
> http://xserve.flids.com/mailman/listinfo/tiff
> 
> 

_______________________________________________
Tiff mailing list
Tiff@remotesensing.org
http://xserve.flids.com/mailman/listinfo/tiff
