pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Anton Voloshin <a.voloshin@postgrespro.ru>
To: Peter Eisentraut <peter@eisentraut.org>
To: Michael Paquier <michael@paquier.xyz>
To: Thomas Munro <thomas.munro@gmail.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: Combine headerscheck and cpluspluscheck scripts
Date: Tue, 16 Apr 2024 18:17:14 +0300
Message-ID: <02e69fa9-885d-4f41-9057-15a1d212eaf8@postgrespro.ru> (raw)
In-Reply-To: <ccf5472b-680f-4021-a0d5-79517c1f7aec@eisentraut.org>
References: <4754a5b0-a32b-4036-a99a-6de14cf9fd72@eisentraut.org>
	<CA+hUKGK360ouUTzxiZ-NQ6FfTyug+BiEJBqr6L2PDNLwW3XiPg@mail.gmail.com>
	<ZeltAyz-1IAoDFaj@paquier.xyz>
	<ccf5472b-680f-4021-a0d5-79517c1f7aec@eisentraut.org>

Hello, hackers,

On 10/03/2024 12:03, Peter Eisentraut wrote:
> Committed, thanks.

This commit (7b8e2ae2f) have turned cpluspluscheck script into a 
--cplusplus option for headerscheck.  I propose to update the 
src/tools/pginclude/README correspondingly, please see the attached patch.

-- 
Anton Voloshin
Postgres Professional, The Russian Postgres Company
https://postgrespro.ru

Attachments:

0001-Update-src-tools-pginclude-README-to-match-recent-ch.patch (text/x-patch, 2.5K) download From a50e58f117341e8a9df5f97fa05630f7b8f4bd86 Mon Sep 17 00:00:00 2001 From: Anton Voloshin <a.voloshin@postgrespro.ru> Date: Tue, 16 Apr 2024 17:19:28 +0300 Subject: [PATCH] Update src/tools/pginclude/README to match recent changes to cpluspluscheck 7b8e2ae2f have turned cpluspluscheck from separate script into a --cplusplus option for headerscheck. Update README correspondingly. --- src/tools/pginclude/README | 24 ++++++++++++------------ 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/src/tools/pginclude/README b/src/tools/pginclude/README index 712eca76fb3..65372057dad 100644 --- a/src/tools/pginclude/README +++ b/src/tools/pginclude/README @@ -1,10 +1,10 @@ src/tools/pginclude/README -NOTE: headerscheck and cpluspluscheck are in current use, and any -problems they find should generally get fixed. The other scripts -in this directory have not been used in some time, and have issues. -pgrminclude in particular has a history of creating more problems -than it fixes. Be very wary of applying their results blindly. +NOTE: headerscheck and headerscheck --cplusplus are in current use, and any +problems they find should generally get fixed. The other scripts in this +directory have not been used in some time, and have issues. pgrminclude in +particular has a history of creating more problems than it fixes. Be very +wary of applying their results blindly. pginclude @@ -84,16 +84,16 @@ prerequisite, even if postgres_fe.h or c.h would be more appropriate. Also note that the contents of macros are not checked; this is intentional. -cpluspluscheck -============== +headerscheck --cplusplus +======================== -This script can be run to verify that all Postgres include files meet -the project convention that they will compile as C++ code. Although -the project's coding language is C, some people write extensions in C++, -so it's helpful for include files to be C++-clean. +The headerscheck in --cplusplus mode can be run to verify that all Postgres +include files meet the project convention that they will compile as C++ +code. Although the project's coding language is C, some people write +extensions in C++, so it's helpful for include files to be C++-clean. A small number of header files are exempted from this requirement, -and are skipped by the cpluspluscheck script. +and are skipped by the script in the --cplusplus mode. The easy way to run the script is to say "make -s cpluspluscheck" in the top-level build directory after completing a build. You should -- 2.43.2

view thread (6+ messages)  latest in thread

Message-ID: <02e69fa9-885d-4f41-9057-15a1d212eaf8@postgrespro.ru>
Permalink:  ../02e69fa9-885d-4f41-9057-15a1d212eaf8@postgrespro.ru/
Also on:    postgresql.org/message-id/02e69fa9-885d-4f41-9057-15a1d212eaf8@postgrespro.ru

 ·  · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: a.voloshin@postgrespro.ru, peter@eisentraut.org, michael@paquier.xyz, thomas.munro@gmail.com
  Subject: Re: Combine headerscheck and cpluspluscheck scripts
  In-Reply-To: <02e69fa9-885d-4f41-9057-15a1d212eaf8@postgrespro.ru>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox