Re: pgindent vs. git whitespace check

Поиск
Список
Период
Сортировка
Искать
От
Andrew Dunstan
Тема
Re: pgindent vs. git whitespace check
Дата
Msg-id
571da410-bb7c-4037-ee96-18154502f3df@dunslane.net
Ответ на
Re: pgindent vs. git whitespace check (Tom Lane)
Список
Дерево обсуждения
pgindent vs. git whitespace check Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Re: pgindent vs. git whitespace check Alvaro Herrera <alvherre@alvh.no-ip.org>
Re: pgindent vs. git whitespace check Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Re: pgindent vs. git whitespace check Tom Lane <tgl@sss.pgh.pa.us>
Re: pgindent vs. git whitespace check Andrew Dunstan <andrew@dunslane.net>
Re: pgindent vs. git whitespace check John Naylor <john.naylor@enterprisedb.com>
Re: pgindent vs. git whitespace check Tom Lane <tgl@sss.pgh.pa.us>
Re: pgindent vs. git whitespace check Daniel Gustafsson <daniel@yesql.se>
Re: pgindent vs. git whitespace check Bruce Momjian <bruce@momjian.us>
Re: pgindent vs. git whitespace check Daniel Gustafsson <daniel@yesql.se>
Re: pgindent vs. git whitespace check Bruce Momjian <bruce@momjian.us>
Re: pgindent vs. git whitespace check Andrew Dunstan <andrew@dunslane.net>


On 2023-02-22 We 09:52, Tom Lane wrote:
pgindent has never been very kind to non-end-of-line comments, and
I'm not excited about working on making it do so.  As a thought
experiment, what would happen if we reversed course and started
allowing "//" comments?  Naive conversion of this comment could
break the code altogether.  (Plenty of programming languages
don't even *have* non-end-of-line comments.)


I suspect not allowing // is at least a minor annoyance to any new developer we acquire under the age of about 40.


cheers


andrew


--
Andrew Dunstan
EDB: https://www.enterprisedb.com
В списке pgsql-hackers по дате отправления
Предыдущее
От: Tom Lane
Дата:
Следующее
От: Andres Freund
Дата:
FAQ