Re: [HACKERS] Updating line length guidelines

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: [HACKERS] Updating line length guidelines
Дата
Msg-id CA+TgmobYSNDYAXF+RacVSn7K0ATG4Q5n5hCzAQ32fZ65OrbUWg@mail.gmail.com
обсуждение исходный текст
Ответ на [HACKERS] Updating line length guidelines  (Andres Freund <andres@anarazel.de>)
Ответы Re: [HACKERS] Updating line length guidelines  (Michael Paquier <michael.paquier@gmail.com>)
Список pgsql-hackers
On Sun, Aug 20, 2017 at 10:49 AM, Andres Freund <andres@anarazel.de> wrote:
> We currently still have the guideline that code should fit into an 80
> character window. But an increasing amount of the code, and code
> submissions, don't adhere to that (e.g. copy.c, which triggered me to
> write this email). And I mean outside of accepted "exceptions" like
> error messages.  And there's less need for such a relatively tight limit
> these days.  Perhaps we should up the guideline to 90 or 100 chars?

Or maybe we should go the other way and get a little more rigorous
about enforcing that limit.  I realize 80 has nothing on its side but
tradition, but I'm a traditionalist -- and I still do use 80 character
windows a lot of the time.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



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

Предыдущее
От: Michael Paquier
Дата:
Сообщение: Re: [HACKERS] Update low-level backup documentation to match actual behavior
Следующее
От: Michael Paquier
Дата:
Сообщение: Re: [HACKERS] Updating line length guidelines