Re: On /*----- comments - Mailing list pgsql-hackers

From Tom Lane
Subject Re: On /*----- comments
Date
Msg-id 879138.1688495803@sss.pgh.pa.us
Whole thread Raw
In response to Re: On /*----- comments  (Heikki Linnakangas <hlinnaka@iki.fi>)
Responses Re: On /*----- comments  (Heikki Linnakangas <hlinnaka@iki.fi>)
List pgsql-hackers
Heikki Linnakangas <hlinnaka@iki.fi> writes:
> On 03/07/2023 11:48, Daniel Gustafsson wrote:
> On 30 Jun 2023, at 17:22, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>> Seems reasonable; the trailing dashes eat a line without adding much.

>> +1

> Pushed a patch to remove the end-guard from the example in the pgindent 
> README. And fixed the bogus end-guard in walsender.c.

I don't see any actual push?

> I'm not sure there is a universal best length. It depends on the comment 
> what looks best. The very long ones in particular would not look good on 
> comments in a deeply indented block. So I think the status quo is fine.

OK, no strong feeling about that here.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Cleaning up array_in()
Next
From: Nathan Bossart
Date:
Subject: Re: O(n) tasks cause lengthy startups and checkpoints