You need to log in before you can comment on or make changes to this bug.
The Changelog of v4.0.0 clearly stated they are 64-bit types, and indeed they are... so they should be uint64** . The bottom of it also says 'March 18, 2005', which explains it. On a related note, is there a v3 to v4 migration guide? I know v4 has been out for years... Most the the other changes I needed to do to migrate an application from v3.9.x to v4 are obvious, from compiler warnings, except this one - this one took me 3 weeks as TIFFGetField takes pointers as arguments, so it does not generate a warning when the argument changed from uint32** to uint64** . I am wondering if there are other GOTCHA's.
Bugzilla is no longer used for tracking libtiff issues. Remaining open tickets, such as this one, have been migrated to the libtiff GitLab instance at https://gitlab.com/libtiff/libtiff/issues . The migrated tickets have their summary prefixed with [BZ#XXXX] where XXXX is the initial Bugzilla issue number.
