On Wed, Jan 8, 2014 at 2:03 PM, Jim Jagielski <firstname.lastname@example.org> wrote:
On Jan 7, 2014, at 3:15 PM, Jeff Trawick <email@example.com> wrote:
> +1 for APR trunk, +0.9 for future APR 1.6.x, -0.9 for APR 1.5.x...
> alternate opinions?
As far as I know, C guarantees that
is the same as
if (a != 0)
So I'm unsure of the need for this patch.
The real question is, for an "unsigned a != 0", can "(int)a" become 0 after an implicit (undefined) conversion?