Re: \if, \elseif, \else, \endif (was Re: [HACKERS] PSQL commands:\quit_if, \quit_unless) - Mailing list pgsql-hackers

From Corey Huinker
Subject Re: \if, \elseif, \else, \endif (was Re: [HACKERS] PSQL commands:\quit_if, \quit_unless)
Date
Msg-id CADkLM=e=4Wi0Gs+sJ=NHw5A++Gay_wXk4ZYSrbgZ7-M52=utwg@mail.gmail.com
Whole thread Raw
In response to Re: \if, \elseif, \else, \endif (was Re: [HACKERS] PSQL commands:\quit_if, \quit_unless)  (Fabien COELHO <coelho@cri.ensmp.fr>)
List pgsql-hackers

As I understood it, the negative feeback was really about sh inspiration "if/fi", not about elif/elsif/elseif. I do not think that there was an
expressed consensus about the later.

True
 
The closest case is CPP with its line-oriented #-prefix syntax, and I still think that we should do it like that.

Given that the pl/pgsql syntax has a space between "end" and "if", I have to agree. It's easy enough to change back if others can make a convincing argument for something else.

pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: [HACKERS] pageinspect: Hash index support
Next
From: Jia Yu
Date:
Subject: Re: [HACKERS] IndexBuild Function call fcinfo cannot access memory