Return-Path: <tiff-bounces@remotesensing.org>
Received: from inmx005.isp.belgacom.be (inmx005.isp.belgacom.be [195.238.3.148])
        by mailst034.isp.belgacom.be (8.12.11/8.12.11/Skynet-MAILSTORE-2.14) with ESMTP id i8HF3mT5025752
        for <joris.at.lebbeke@skynet.be>; Fri, 17 Sep 2004 17:03:48 +0200
        (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 i8HF3gHg012248
        for <joris.at.lebbeke@skynet.be>; Fri, 17 Sep 2004 17:03:43 +0200
        (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 4F58A2F633C; Fri, 17 Sep 2004 11:03:29 -0400 (EDT)
X-Original-To: tiff@remotesensing.org
Delivered-To: tiff@remotesensing.org
Received: from visa.com (portal3.visa.com [198.80.42.3])
	by xserve.flids.com (Postfix) with ESMTP id 8CCBC2F6319
	for <tiff@remotesensing.org>; Fri, 17 Sep 2004 11:03:26 -0400 (EDT)
Received: from ([10.72.86.29]) by portal3.visa.com with ESMTP ;
	Fri, 17 Sep 2004 08:02:54 -0700 (PDT)
Received: from sw720ex016.visa.com ([10.72.11.170]) by sw720ex001.visa.com
	with Microsoft SMTPSVC(5.0.2195.6713); 
	Fri, 17 Sep 2004 08:02:54 -0700
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Tiff] BigTIFF Tag Value Count issue
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
Date: Fri, 17 Sep 2004 08:10:02 -0700
Message-ID: <4BCF88971C5D964094550DF1B35532A81F2DE4@sw720ex016.visa.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Tiff] BigTIFF Tag Value Count issue
Thread-Index: AcScuP/Se3ymPbntS3qdnCu09jGKvgADKPGA
From: "Loygorri, Fernando" <FLoygorr@inovant.com>
To: "TIFF Mailing List" <tiff@remotesensing.org>
X-OriginalArrivalTime: 17 Sep 2004 15:02:54.0537 (UTC)
	FILETIME=[68E35390:01C49CC7]
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: 62243df28a52112284d92021ebb8bb4d

> >>Does anyone know if stuff like PDA's and such have efficient-to-use
> >>64bit integer datatypes?  I am somewhat doubtful.

Java data types are all signed, so the maximum positive value of an =
8-bit
long is cut in half.

> > Is it allowable to have BigTIFF not work on those machines,=20
> but have classic
> > TIFF still in working order? Perhaps a structure like...
> >=20
> > #ifdef BIGTIFF_SUPPORT
> > if file is tiff classic {
> > #endif
> >   tiff classic supporting code
> >   ** this includes reporting error when suffering the consequences
> >        of getting a BigTIFF file **
> > #ifdef BIGTIFF_SUPPORT
> > } else {
> >   bigtiff supporting code
> > }
> > #endif

I understand that libtiff is written in C, but I believe that a TIFF
specification should not assume anything about implementation languages.

If BigTIFF defines unsigned 64-bit quantities, it will make life for
Java applications more difficult and possibly slower, although not
impossible.

Regards,

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