From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Updating line length guidelines |
Date: | 2017-08-21 02:30:03 |
Message-ID: | CA+TgmobYSNDYAXF+RacVSn7K0ATG4Q5n5hCzAQ32fZ65OrbUWg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, Aug 20, 2017 at 10:49 AM, Andres Freund <andres(at)anarazel(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2017-08-21 02:36:43 | Re: Updating line length guidelines |
Previous Message | Michael Paquier | 2017-08-21 02:22:17 | Re: Update low-level backup documentation to match actual behavior |