aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPeter Eisentraut <peter@eisentraut.org>2019-09-26 10:51:39 +0200
committerPeter Eisentraut <peter@eisentraut.org>2019-09-26 10:52:19 +0200
commitb4d615aaa1ecedcf1e2ca415cd2893d1f18aeeca (patch)
tree90ea229ca99ea6b6b4c57fab91ce89932b1802f5
parent66e0ea75bb9d4b40c734067dd7c7e1fc804a88cb (diff)
downloadpostgresql-b4d615aaa1ecedcf1e2ca415cd2893d1f18aeeca.tar.gz
postgresql-b4d615aaa1ecedcf1e2ca415cd2893d1f18aeeca.zip
doc: Update note about source code formatting
Update the note about why not to use // comments, even though it's now technically supported. The note about variable declarations was dropped here because it's addressed more properly later in the chapter. Discussion: https://www.postgresql.org/message-id/flat/156924954640.1117.6309209869705522549%40wrigleys.postgresql.org
-rw-r--r--doc/src/sgml/sources.sgml6
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/src/sgml/sources.sgml b/doc/src/sgml/sources.sgml
index 6294312ab7d..25e7763c7c7 100644
--- a/doc/src/sgml/sources.sgml
+++ b/doc/src/sgml/sources.sgml
@@ -26,9 +26,9 @@
</para>
<para>
- Do not use C++ style comments (<literal>//</literal> comments). Strict ANSI C
- compilers do not accept them. For the same reason, do not use C++
- extensions such as declaring new variables mid-block.
+ To maintain a consistent coding style, do not use C++ style comments
+ (<literal>//</literal> comments). <application>pgindent</application>
+ will replace them with <literal>/* ... */</literal>.
</para>
<para>