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
