Horton

Re: [HACKERS] taking stdbool.h into use

Michael Paquier <michael@paquier.xyz>

View thread View on postgr.es
From: Michael Paquier <michael@paquier.xyz>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Andres Freund <andres@anarazel.de>, pgsql-hackers@lists.postgresql.org, Alvaro Herrera <alvherre@alvh.no-ip.org>, Thomas Munro <thomas.munro@enterprisedb.com>
Date: 2018-03-22T01:42:20Z
Lists: pgsql-hackers 
On Wed, Mar 21, 2018 at 07:48:02AM -0400, Peter Eisentraut wrote:
> I've pushed the configure tests.  Let's see what they say.

At least the buildfarm is green.  Browsing the buildfarm logs manually
is kind of annoying for any normal human being.  I guess that you have
access to the database holding all this data, which could make that
easier to look.  What are those telling about SIZEOF_BOOL in
pg_config.h?
--
Michael

Commits

  1. Use stdbool.h if suitable

  2. Add configure tests for stdbool.h and sizeof bool

  3. Remove useless use of bit-masking macros

  4. Change various Gin*Is* macros to return 0/1.

  5. Fix several possibly non-portable gaffs in record_image_ops.