pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
Cc: Noah Misch <noah@leadboat.com>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: cleaning perl code
Date: Thu, 16 Apr 2020 09:53:46 -0400
Message-ID: <4426.1587045226@sss.pgh.pa.us> (raw)
In-Reply-To: <ee6dff48-485d-974d-cc68-67ee86fe73b8@2ndQuadrant.com>
References: <20200414204432.GA22922@alvherre.pgsql>
	<86b0e20d-efc1-4169-aeb1-be49b3a375ab@2ndQuadrant.com>
	<20200416030101.GB977691@rfd.leadboat.com>
	<ee6dff48-485d-974d-cc68-67ee86fe73b8@2ndQuadrant.com>

Andrew Dunstan <andrew.dunstan@2ndquadrant.com> writes:
> On 4/15/20 11:01 PM, Noah Misch wrote:
>> It would be an unpleasant surprise to cause a perlcritic buildfarm failure by
>> moving a function, verbatim, from a non-strategic file to a strategic file.
>> Having two Perl style regimes in one tree is itself a liability.

> Honestly, I think you're reaching here.

I think that argument is wrong, actually.  Moving a function from a single
use-case into a library (with, clearly, the intention for it to have more
use-cases) is precisely the time when any weaknesses in its original
implementation might be exposed.  So extra scrutiny seems well warranted.

Whether the "extra scrutiny" involved in perlcritic's higher levels
is actually worth anything is a different debate, though, and so far
it's not looking like it's worth much :-(

			regards, tom lane





view thread (34+ messages)  latest in thread

Message-ID: <4426.1587045226@sss.pgh.pa.us>
Permalink:  ../4426.1587045226@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/4426.1587045226@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: tgl@sss.pgh.pa.us, andrew.dunstan@2ndquadrant.com, noah@leadboat.com, alvherre@2ndquadrant.com
  Subject: Re: cleaning perl code
  In-Reply-To: <4426.1587045226@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox