From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Boszormenyi Zoltan <zb(at)cybertec(dot)at>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: TRUE/FALSE vs true/false |
Date: | 2012-08-14 21:36:35 |
Message-ID: | 20120814213635.GB15578@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Aug 14, 2012 at 05:34:02PM -0400, Tom Lane wrote:
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > On Thu, Aug 4, 2011 at 09:00:11PM +0300, Peter Eisentraut wrote:
> >> On tor, 2011-08-04 at 14:44 +0200, Boszormenyi Zoltan wrote:
> >>> I meant a mass "sed -e 's/TRUE/true/g' -e 's/FALSE/false/g'" run
> >>> so all the ~200 occurrences of both "TRUE" and "FALSE" get
> >>> converted so the whole source tree is consistent.
>
> >> I would be in favor of that.
>
> > I have implemented this with the patch at:
> > http://momjian.us/expire/true_diff.txt
>
> Does this really do anything for us that will justify the extra
> back-patching pain it will cause? I don't see that it's improving
> code readability any.
I think it is more of a consistency issue. There were multiple people
who wanted this change. Of course, some of those people don't backport
stuff.
Other comments?
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2012-08-14 21:41:09 | Re: GetSnapshotData() comments |
Previous Message | Tom Lane | 2012-08-14 21:34:02 | Re: TRUE/FALSE vs true/false |