Re: PRI_stime

[Juergen Gross <jgross@suse.com>]

On 10/20/2015 10:10 AM, George Dunlap wrote:
> On Tue, Oct 20, 2015 at 7:26 AM, Jan Beulich <JBeulich@suse.com> wrote:
>> George, Dario,
>>
>> it being mostly used in scheduler code, and me considering it quite a
>> bit easier to compare such big numbers when shown in hex I wonder:
>> Do you prefer this to stay PRId64, or would you accept it to be
>> changed to PRIx64 (allowing it to be used in a few other places)?
>
> Personally I've never taken the time to familiarize myself with the
> magnitude of hex numbers vs decimal numbers; so in the case of time, I
> could easily see that 10000000 nanoseconds is about 1ms; but I don't

A good example for doing it in hex. Less digits are less error prone.
Your example would translate to 10ms. :-)

> have a good sense of how long 0x1000000 nanoseconds is.  The fact that

0x100000 is about 1 million. This helps a lot to get an idea of the
magnitude.

> our times are based on base 10 instead of base 2 is I think as good an
> argument as any for leaving it as a decimal.
>
> But I wouldn't oppose the change if Dario (or others) thought x64 was
> the way to go.

+1 for hex.


Juergen