Re: [HACKERS] taking stdbool.h into use - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: [HACKERS] taking stdbool.h into use
Date
Msg-id CAB7nPqQ0mok+6VkJ06xdB74pgqbuAOnwkHvmBWQWU58bsSPOVg@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] taking stdbool.h into use  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Responses Re: [HACKERS] taking stdbool.h into use
List pgsql-hackers
On Thu, Oct 26, 2017 at 10:51 AM, Alvaro Herrera
<alvherre@alvh.no-ip.org> wrote:
> I gave this a quick run, to see if my compiler would complain for things
> like this:
>
>    bool        isprimary = flags & INDEX_CREATE_IS_PRIMARY;
>
> (taken from the first patch at
> https://postgr.es/m/20171023161503.ohkybquxrlech7d7@alvherre.pgsql )
>
> which is assigning a value other than 1/0 to a bool variable without an
> explicit cast.  I thought it would provoke a warning, but it does not.
> Is that expected?  Is my compiler too old/new?

It seems to me that this proves the point of the proposed patch. You
had better use a zero-equality comparison for such bitwise operation,
and so you ought to do that:
bool        isprimary = (flags & INDEX_CREATE_IS_PRIMARY) != 0;
-- 
Michael


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] proposal: custom autovacuum entries
Next
From: Michael Paquier
Date:
Subject: Re: [HACKERS] proposal: custom autovacuum entries