Re: pgsql: Use stdbool.h if suitable

From: Andres Freund <andres(at)anarazel(dot)de>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Use stdbool.h if suitable
Date: 2018-03-23 05:22:33
Message-ID: 20180323052233.sjq26vqkdg5txrxg@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Hi,

On 2018-03-23 00:42:39 +0000, Peter Eisentraut wrote:
> Use stdbool.h if suitable
>
> Using the standard bool type provided by C allows some recent compilers
> and debuggers to give better diagnostics. Also, some extension code and
> third-party headers are increasingly pulling in stdbool.h, so it's
> probably saner if everyone uses the same definition.
>
> But PostgreSQL code is not prepared to handle bool of a size other than
> 1, so we keep our own old definition if we encounter a stdbool.h with a
> bool of a different size. (Among current build farm members, this only
> applies to old macOS versions on PowerPC.)
>
> To check that the used bool is of the right size, add a static
> assertions about size of GinTernaryValue vs bool. This is currently the
> only place that assumes that bool and char are of the same size.

This appears to have broken buildfarm animal locust:

https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=locust&dt=2018-03-23%2001%3A13%3A30

I suspect that's because of the perl hunk
> src/pl/plperl/plperl.h | 10 +++++-----

Greetings,

Andres Freund

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Andres Freund 2018-03-23 05:36:22 pgsql: Adapt expression JIT to stdbool.h introduction.
Previous Message Peter Eisentraut 2018-03-23 02:36:28 pgsql: Fix whitespace