Return-Path: <tiff-bounces@lists.maptools.org>
X-Original-To: info@awaresystems.be
Delivered-To: info@awaresystems.be
Received: from mx-j.b-one.net (mx-j.one.com [91.198.169.57])
	by mail9.b-one.net (Postfix) with ESMTP id 8E44E40024F
	for <info@awaresystems.be>; Fri, 18 Jun 2010 00:35:07 +0200 (CEST)
Received: by mx-j.b-one.net (Postfix, from userid 106)
	id 84FAE46775A9; Fri, 18 Jun 2010 00:35:07 +0200 (CEST)
X-Virus-Scanned: by one.com
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.4
Received: from lists.maptools.org (lists.maptools.org [65.39.174.144]) by
 mx-j.b-one.net (Postfix) with ESMTP id A7CE946775AC for
 <info@awaresystems.be>; Fri, 18 Jun 2010 00:35:06 +0200 (CEST)
Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by
 lists.maptools.org (Postfix) with ESMTP id 27D451D18E136; Thu, 17 Jun 2010
 17:34:01 -0500 (EST)
Received: from mail.sidefx.com (mail.sidefx.com [38.99.137.163]) by
 lists.maptools.org (Postfix) with ESMTP id 346C61CF4D102 for
 <tiff@lists.maptools.org>; Thu, 17 Jun 2010 17:06:52 -0500 (EST)
Message-ID: <4C1A9C73.1020605@sidefx.com>
Date: Thu, 17 Jun 2010 18:06:43 -0400
From: Edward Lam <edward@sidefx.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Adam Goode <adam@spicenitz.org>
References: <4C1A41A5.4070409@spicenitz.org> <4C1A4B72.2020705@sidefx.com>
 <4C1A4F92.2090902@spicenitz.org>
In-Reply-To: <4C1A4F92.2090902@spicenitz.org>
Cc: tiff@lists.maptools.org
Subject: Re: [Tiff] libtiff 4 API/ABI stability?
X-BeenThere: tiff@lists.maptools.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TIFF and libtiff discussion <tiff.lists.maptools.org>
List-Unsubscribe: <http://lists.maptools.org/mailman/listinfo/tiff>,
 <mailto:tiff-request@lists.maptools.org?subject=unsubscribe>
List-Archive: <http://lists.maptools.org/mailman/private/tiff>
List-Post: <mailto:tiff@lists.maptools.org>
List-Help: <mailto:tiff-request@lists.maptools.org?subject=help>
List-Subscribe: <http://lists.maptools.org/mailman/listinfo/tiff>,
 <mailto:tiff-request@lists.maptools.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tiff-bounces@lists.maptools.org
Errors-To: tiff-bounces@lists.maptools.org

Adam Goode wrote:
> On 06/17/2010 12:21 PM, Edward Lam wrote:
>> Adam Goode wrote:
>>> I was wondering if there are going to be any API or ABI incompatible
>>> changes before the final release of libtiff 4.
>> If you care about Windows, bug 1941 [1] is still open. If it gets fixed,
>> then the behaviour for the following functions will change on Windows:
>> TIFFFdOpen(), TIFFFileno(), TIFFSetFileno(), TIFFClientdata(),
>> TIFFSetClientdata().
> 
> I am not quite as concerned with Windows behavior as Unix, since
> shipping dependent DLLs is the norm on Windows, but this could change if
> CoApp[1] becomes popular (as I hope it does).
> 
> I think this should be fixed before libtiff 4. Is anyone interested in
> making a release blocker bug in bugzilla? We could add this bug to it.

I could if we get some maintainer is willing to look at it for libtiff 4.

> Also, I wonder why the tif_win32.c file isn't enabled by default on
> Windows. With tif_unix.c, the file interface is limited to 2GB on
> Windows. tif_win32.c is needed for large file access (the whole point of
> libtiff 4?).

Sorry, I think that I'm wrong on this. It does look like tif_win32.c is 
the default. On the note of tif_unix.c for Windows, I think we only need 
to patch it _lseeki64 to work for large files?

Regards,
-Edward
_______________________________________________
Tiff mailing list: Tiff@lists.maptools.org
http://lists.maptools.org/mailman/listinfo/tiff
http://www.remotesensing.org/libtiff/
