| From: | Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru> |
|---|---|
| To: | Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: TRUE and true |
| Date: | 2017-06-22 12:35:13 |
| Message-ID: | CAPpHfdtsF13YM1jbKCDBrdeC2Da5vs9Ca6sL4rwRj6=h1ACZgw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jun 22, 2017 at 2:09 PM, Kyotaro HORIGUCHI <
horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp> wrote:
> Hello, I have a maybe-silly question.
>
> What makes us have both TRUE/true or FALSE/false as constants of
> bool?
>
> The following definitions in c.h didn't mess anything up.
>
> #define TRUE true
> #define FALSE false
>
+1
I don't know any policy about where to use TRUE and FALSE over true and
false.
# NIL seems causing similar mess.
>
NIL is used for lists, while NULL is used for other pointers.
That may cause redundant, but at least there is clear policy.
------
Alexander Korotkov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2017-06-22 12:51:14 | Re: SQL MERGE patches for PostgreSQL Versions |
| Previous Message | Alexander Korotkov | 2017-06-22 12:32:00 | Re: Pluggable storage |