| From: | Mike Blackwell <mike(dot)blackwell(at)rrd(dot)com> |
|---|---|
| To: | David Fetter <david(at)fetter(dot)org> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: perlcritic |
| Date: | 2015-09-01 15:58:09 |
| Message-ID: | CANPAkgtDa1AOh5k+Gs63PVuM9FpNK=G1XdCSF+OtKTnKf3hpog@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
David wrote:
> I believe there are ways to get perlcritic to keep quiet about things
> we don't find relevant. Maybe that's a better way to use it.
>
There are indeed. A .perlcriticrc file can suppress (or add) either
individual rules or groups of rules. I use one to ignore the ones I
disagree with, along with the comment form to ignore specific cases.
I see perlcritic as functioning for me along the same lines as a style
guide, giving a consistency that helps with long term maintainability.
It also helps keep me from straying into golf. ^_^
| From | Date | Subject | |
|---|---|---|---|
| Next Message | YUriy Zhuravlev | 2015-09-01 15:59:29 | Re: WIP: About CMake v2 |
| Previous Message | Roger Pack | 2015-09-01 15:56:59 |