On 32 bits u can use 64 bit offsets without issues.. Just have to put
some defines before #include
Ilinux have all io syscalls dupped for 32 and 64 (open, open64, read,
read64...)
In bsd 32bit calls are just wrapped inside the 64 bit ones.
But really..64bit offsets are ok, but 64bit length... Is certainly
stupid. Not because u can it's good to do.. Make the test and u will
end up with a totally unresponsible app that makes the whole system go
slow just for a single syscall with not recommended way to use it.
As I said. Make the test and u will understand.
On Jun 12, 2010, at 8:16 AM, Kris Maglione <maglion...@gmail.com> wrote:
On Sat, Jun 12, 2010 at 07:05:34AM +0100, Connor Lane Smith wrote:
On 12 June 2010 06:59, Kris Maglione <maglion...@gmail.com> wrote:
The size of size_t and ssize_t are irrelevant when
you're talking about a function that isn't guaranteed or expected
to return
any specific amount of data on a specific call.
Let me run that by you again:
On 12 June 2010 02:42, Kris Maglione <maglion...@gmail.com> wrote:
The only limitation is that if you want
more than 2GB, you need to make multiple calls.
No you don't.
Are we talking about in some hypothetical world where all computers
are 64 bit or all C libraries define ssize_t to be a 64 bit int, or
are we talking about practical reality, where most computers are
still 32 bit and nearly all C libraries define size_t as the size of
a machine word (and are highly unlikely to ever do different)?
--
Kris Maglione
It is a miracle that curiosity survives formal education.
--Albert Einstein
