Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pIuTb-0003Au-13 for pgsql-hackers@arkaria.postgresql.org; Fri, 20 Jan 2023 16:42:51 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pIuTX-00068k-Vj for pgsql-hackers@arkaria.postgresql.org; Fri, 20 Jan 2023 16:42:47 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pIuTX-00068O-Mr for pgsql-hackers@lists.postgresql.org; Fri, 20 Jan 2023 16:42:47 +0000 Received: from momjian.us ([72.94.173.45]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pIuTU-00018J-Vn for pgsql-hackers@postgresql.org; Fri, 20 Jan 2023 16:42:46 +0000 Received: from bruce by momjian.us with local (Exim 4.94.2) (envelope-from ) id 1pIuTJ-003uIn-UG; Fri, 20 Jan 2023 11:42:33 -0500 Date: Fri, 20 Jan 2023 11:42:33 -0500 From: Bruce Momjian To: Jelte Fennema Cc: Magnus Hagander , Alvaro Herrera , Stephen Frost , Tom Lane , Noah Misch , Jesse Zhang , Andres Freund , PostgreSQL-development Subject: Re: run pgindent on a regular basis / scripted manner Message-ID: References: <20200814202651.GA31108@alvherre.pgsql> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Fri, Jan 20, 2023 at 10:43:50AM +0100, Jelte Fennema wrote: > Side-question: What's the reason why pgindent is used instead of some > more "modern" code formatter that doesn't require keeping > typedefs.list up to date for good looking output? (e.g. uncrustify or > clang-format) Because that would also allow for easy editor > integration. Good question. Our last big pgindent dicussion was in 2017, where I said: https://www.postgresql.org/message-id/flat/20170612213525.GA4074%40momjian.us#a96eac96c147ebcc1de86fe2356a160d Understood. You would think that with the number of open-source programs written in C that there would be more interest in C formatting tools. Is the Postgres community the only ones with specific requirements, or is it just that we settled on an older tool and can't easily change? I have reviewed the C formatting options a few times over the years and every time the other options were worse than what we had. We also discussed it in 2011, and this email was key for me: https://www.postgresql.org/message-id/flat/201106220218.p5M2InB08144%40momjian.us#096cbcf02cb58c7d6c49bc79d2c79317 I am excited Andrew has done this. It has been on my TODO list for a while --- I was hoping someday we could switch to GNU indent but gave up after the GNU indent report from Greg Stark that exactly matched my experience years ago: http://archives.postgresql.org/pgsql-hackers/2011-04/msg01436.php Basically, GNU indent has new bugs, but bugs that are harder to work around than the BSD indent bugs. -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Embrace your flaws. They make you human, rather than perfect, which you will never be.