AWARE SYSTEMS
TIFF and LibTiff Mail List Archive

Thread

2009.08.20 23:12 "[Tiff] Libtiff 3.9.0 Released", by Bob Friesenhahn
2009.08.21 05:14 "Re: [Tiff] Libtiff 3.9.0 Released", by Tom Lane
2009.08.21 14:16 "Re: [Tiff] Libtiff 3.9.0 Released", by Bob Friesenhahn
2009.08.21 15:26 "Re: [Tiff] Libtiff 3.9.0 Released", by Jay Berkenbilt
2009.08.21 16:27 "Re: [Tiff] Libtiff 3.9.0 Released", by Bob Friesenhahn
2009.08.21 17:12 "Re: [Tiff] Libtiff 3.9.0 Released", by Jay Berkenbilt
2009.08.27 18:13 "[Tiff] Libtiff 4.4.0beta4 Released", by Bob Friesenhahn
2009.08.27 18:55 "Re: [Tiff] Libtiff 4.4.0beta4 Released", by Edward Lam
2009.08.27 19:07 "Re: [Tiff] Libtiff 4.4.0beta4 Released", by Bob Friesenhahn
2009.08.27 19:14 "Re: [Tiff] Libtiff 4.4.0beta4 Released", by Frank Warmerdam
2009.08.27 19:01 "Re: [Tiff] Libtiff 4.4.0beta4 Released", by Edward Lam
2009.08.27 19:15 "Re: [Tiff] Libtiff 4.4.0beta4 Released", by Bob Friesenhahn
2009.08.28 19:09 "[Tiff] Libtiff 3.9.1 Released", by Bob Friesenhahn

2009.08.27 19:01 "Re: [Tiff] Libtiff 4.4.0beta4 Released", by Edward Lam

The most common problem is with code which assumes that a returned file offset or size can be stored in a 32-bit type.

Are there tag values that have been changed from 32-bit to 64-bit? Does it still work if we call something like:

     TIFFSetField(myTiff, TIFFTAG_ROWSPERSTRIP, rowsperstrip);

where rowsperstrip is a 32-bit integer?

Thanks,

-Edward