From 42765f2c360e3594fe921a65be94b5e37f303655 Mon Sep 17 00:00:00 2001 From: Roland Schulz Date: Thu, 23 Aug 2018 21:20:08 -0700 Subject: [PATCH] Add hard limit for line length Extremely long lines are a pain in diff-views (gerrit, github, ...), and a problem for readability. The specific number doesn't matter, as long as it reasonable. Most of us are just ignoring 80 so that is useless as guideline. Change-Id: I5dbced451b56bc307beea2aec7599b8764f978cd --- docs/dev-manual/formatting.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/dev-manual/formatting.rst b/docs/dev-manual/formatting.rst index e8f0659232..15efc0562e 100644 --- a/docs/dev-manual/formatting.rst +++ b/docs/dev-manual/formatting.rst @@ -7,9 +7,9 @@ The following list provides the general formatting/indentation rules for |Gromacs| code (C/C++): * Basic indentation is four spaces. -* Keep lines at a reasonable length. There is no hard limit, but use 80 - characters as a guideline. If you end up indenting very deeply, - consider splitting the code into functions. +* Keep lines at a reasonable length. Keep every line at least below 120 + characters. If you end up indenting very deeply, consider splitting the code + into functions. * Do not use tabs, only spaces. Most editors can be configured to generate spaces even when pressing tab. Tabs (in particular when mixed with spaces) easily break indentation in contexts where settings are not exactly equal -- 2.11.4.GIT