Re: perlcritic and perltidy

From: Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>
To: David Steele <david(at)pgmasters(dot)net>, Stephen Frost <sfrost(at)snowman(dot)net>, Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: perlcritic and perltidy
Date: 2018-05-08 16:19:39
Message-ID: 5b5e8c07-1fd0-7d51-92a4-4d8f0f0f0891@2ndQuadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 05/08/2018 10:06 AM, Andrew Dunstan wrote:
> {         find . -type f -a \( -name
> '*.pl' -o -name '*.pm' \) -print;         find . -type f -perm -100
> -exec file {} \; -print                | egrep -i
> ':.*perl[0-9]*\>'                | cut -d: -f1;     }     | sort -u  |
> xargs perlcritic --quiet --single CodeLayout::RequireTrailingCommas

Here's a diff of all the places it found fixed. At this stage I don't
think it's worth it. If someone wants to write a perlcritic policy that
identifies missing trailing commas reasonably comprehensively, we can
look again. Otherwise we should just clean them up as we come across them.

cheers

andrew

--
Andrew Dunstan https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

Attachment Content-Type Size
missing-comma.diff text/x-patch 10.3 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2018-05-08 16:27:52 Re: [HACKERS] path toward faster partition pruning
Previous Message Peter Eisentraut 2018-05-08 16:16:48 Re: perlcritic and perltidy