diff options
| author | Peter Eisentraut | 2017-08-16 04:22:32 +0000 |
|---|---|---|
| committer | Peter Eisentraut | 2017-11-08 16:37:28 +0000 |
| commit | 2eb4a831e5fb5d8fc17e13aea56e04af3efe27b4 (patch) | |
| tree | b46993cceb7cd8b848e39a45c1bb8c73dc67b221 /contrib/btree_gist/btree_bit.c | |
| parent | 4497f2f3b30fa5cd48898033c351bfcf01ce73e2 (diff) | |
Change TRUE/FALSE to true/false
The lower case spellings are C and C++ standard and are used in most
parts of the PostgreSQL sources. The upper case spellings are only used
in some files/modules. So standardize on the standard spellings.
The APIs for ICU, Perl, and Windows define their own TRUE and FALSE, so
those are left as is when using those APIs.
In code comments, we use the lower-case spelling for the C concepts and
keep the upper-case spelling for the SQL concepts.
Reviewed-by: Michael Paquier <[email protected]>
Diffstat (limited to 'contrib/btree_gist/btree_bit.c')
| -rw-r--r-- | contrib/btree_gist/btree_bit.c | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/contrib/btree_gist/btree_bit.c b/contrib/btree_gist/btree_bit.c index a56a2752a73..2225244ded5 100644 --- a/contrib/btree_gist/btree_bit.c +++ b/contrib/btree_gist/btree_bit.c @@ -111,7 +111,7 @@ static const gbtree_vinfo tinfo = { gbt_t_bit, 0, - TRUE, + true, gbt_bitgt, gbt_bitge, gbt_biteq, @@ -152,13 +152,13 @@ gbt_bit_consistent(PG_FUNCTION_ARGS) if (GIST_LEAF(entry)) retval = gbt_var_consistent(&r, query, strategy, PG_GET_COLLATION(), - TRUE, &tinfo, fcinfo->flinfo); + true, &tinfo, fcinfo->flinfo); else { bytea *q = gbt_bit_xfrm((bytea *) query); retval = gbt_var_consistent(&r, q, strategy, PG_GET_COLLATION(), - FALSE, &tinfo, fcinfo->flinfo); + false, &tinfo, fcinfo->flinfo); } PG_RETURN_BOOL(retval); } |