Re: pgsql: Sync our regex code with upstream changes since last time we did - Mailing list pgsql-committers

From Bruce Momjian
Subject Re: pgsql: Sync our regex code with upstream changes since last time we did
Date
Msg-id 200802162258.m1GMwTX16095@momjian.us
Whole thread Raw
In response to Re: pgsql: Sync our regex code with upstream changes since last time we did  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-committers
Alvaro Herrera wrote:
> Andrew Dunstan wrote:
> >
> >
> > Tom Lane wrote:
> >> Note that I didn't make any effort to duplicate a lot of cosmetic changes
> >> that they made to bring their copy into line with their own style
> >> guidelines, such as adding braces around single-line IF bodies.  Most of
> >> those we either had done already (such as ANSI-fication of function headers)
> >> or there is no point because pgindent would undo the change anyway.
> >
> > Not objecting, but IIRC we disabled the pgindent code that removes
> > braces around single line (or rather statement) IF bodies several years
> > ago.
>
> Yeah, we did, because it was removing the braces around PG_TRY()
> constructs.

We removed it because people didn't like changes to cases like:

    if ()
    {
        a;
    }
    else
    {
        b;
    }

I don't remember an issue with PG_TRY, which I could have fixed.

--
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://postgres.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

pgsql-committers by date:

Previous
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Update docs to reflect the fact that we can now deal with DST
Next
From: momjian@postgresql.org (Bruce Momjian)
Date:
Subject: pgsql: Move item as done: < > * -Allow AS in "SELECT col AS label" to