Re: perlcritic and perltidy

Stephen Frost <sfrost@snowman.net>

From: Stephen Frost <sfrost@snowman.net>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>, David Steele <david@pgmasters.net>, Michael Paquier <michael@paquier.xyz>, Tom Lane <tgl@sss.pgh.pa.us>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2018-05-08T17:06:42Z
Lists: pgsql-hackers
Greetings,

* Alvaro Herrera (alvherre@2ndquadrant.com) wrote:
> Stephen Frost wrote:
> 
> > * Andrew Dunstan (andrew.dunstan@2ndquadrant.com) wrote:
> >
> > > -		'XLogRecPtr'    => 'pg_lsn');
> > > +		'XLogRecPtr'    => 'pg_lsn',);
> >
> > There's not much point adding the ',' unless you're also putting the
> > ');' on the next line, is there..?
> > 
> > Or is that going to be handled in a follow-up patch?
> 
> IMO we should classify this one as pointless uglification and move on.

I'm all for the change if we actually get to a result where the lines
can be moved and you don't have to go muck with the extra stuff at the
end of the line (add a comma, or remove a comma, remove or add the
parens, etc).  If we aren't going all the way to get to that point then
I tend to agree that it's not a useful change to make.

Thanks!

Stephen

Commits

  1. Don't force a blank line before comments in perl code

  2. Restrict vertical tightness to parentheses in Perl code