[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: xtime.h's xtime_nsec: s/int/long int/? (resend)

From: Paul Eggert
Subject: Re: xtime.h's xtime_nsec: s/int/long int/? (resend)
Date: Tue, 03 Jan 2006 10:24:39 -0800
User-agent: Gnus/5.1007 (Gnus v5.10.7) Emacs/21.4 (gnu/linux)

Jim Meyering <address@hidden> writes:

> [I sent this message a few weeks ago, but it was
>  mistakenly MIME-format=flowed, so not very readable]

Odd, I sent a reply (only to bug-gnulib), but I see it's not archived
so I guess it didn't get through the spam filters.  Here it is again.


POSIX originally made tv_nsec 'long int' because 'int' might have been
16 bits.  Nowadays, though, 'int' is guaranteed to be at least 32 bits
(both by POSIX and by the GNU coding standards), so it's OK nowadays
to use 'int' to store a tv_nsec number.

I thought it a bit nicer to celebrate the fact that we don't have to
worry about 16-bit hosts, and to use plain 'int' here.  It's not a big
deal either way, though, and if there's a problem with using 'int' we
can change it to 'long int'.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]