Re: proposal: disallow operator "=>" and use it for named parameters

Поиск
Список
Период
Сортировка
От Pavel Stehule
Тема Re: proposal: disallow operator "=>" and use it for named parameters
Дата
Msg-id CAFj8pRDqAdDGMB24uRggirRVyG--5VjxXtdaBysSZ-q4S0jVOA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: proposal: disallow operator "=>" and use it for named parameters  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: proposal: disallow operator "=>" and use it for named parameters  (Petr Jelinek <petr@2ndquadrant.com>)
Список pgsql-hackers
Дерево обсуждения


2015-03-10 16:50 GMT+01:00 Tom Lane <tgl@sss.pgh.pa.us>:
Robert Haas <robertmhaas@gmail.com> writes:
> On Thu, Feb 19, 2015 at 3:15 PM, Pavel Stehule <pavel.stehule@gmail.com> wrote:
>> I am marking this as Ready For Committer, the patch is trivial and works
>> as expected, there is nothing to be added to it IMHO.
>>
>> The "=>" operator was deprecated for several years so it should not be too
>> controversial either.

> Committed with a few documentation tweaks.

Was there any consideration given to whether ruleutils should start
printing NamedArgExprs with "=>"?  Or do we think that needs to wait?

I didn't think about it? I don't see any reason why it have to use deprecated syntax.

Regards

Pavel
 

                        regards, tom lane

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: Stateful C-language function with state managed by third-party library
Следующее
От: Petr Jelinek
Дата:
Сообщение: Re: proposal: disallow operator "=>" and use it for named parameters