Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 05 Jun 2011 21:24:05 +0000
From:      "Poul-Henning Kamp" <phk@phk.freebsd.dk>
To:        Ben Laurie <ben@links.org>
Cc:        hackers@freebsd.org
Subject:   Re: int64_t and printf 
Message-ID:  <12618.1307309045@critter.freebsd.dk>
In-Reply-To: Your message of "Sun, 05 Jun 2011 22:11:03 %2B0100." <4DEBF0E7.3040304@links.org> 

next in thread | previous in thread | raw e-mail | index | archive | help
In message <4DEBF0E7.3040304@links.org>, Ben Laurie writes:

>I note that you didn't react to my other wherein you cast from known
>type A to known type B. I supposed it would be smart to also assert that
>the cast was non-narrowing.

Well, if casting to intmax_t is narrowing I think I have bigger
problems on my hands :-)

I've spent a fair amount of time agonizing over this in Varnish and
I came to the conclusion that the my time spent trying to establish
if something narrower than intmax_t was safe would never amortize
the performance difference of printing an intmax_t vs. intN_t, so
now I just cast anything that that's typedef'ed to intmax_t and
move on.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?12618.1307309045>