On Tue, Dec 7, 2010 at 1:19 PM, Brad King <firstname.lastname@example.org>
Actually there are more reasons to use uint64_t rather than size_t.
Some APIs may support loading a small part of a gigantic image.
In that case the underlying indexing and file offsets must be 64-bit
even though pointers might be only 32-bit. Types like size_t are
good for dealing with in-memory buffers (and thus standard library
APIs) but not for indexing something that might be mostly out-of-core.
BTW, a patch like that attached will be helpful for dealing with 64-bit
integer types. This adds "long long" overloads for vnl_math functions
that are supposed to be available for all fundamental integer types.