Re: Status of plperl inter-sp calling

From: "David E(dot) Wheeler" <david(at)kineticode(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Tim Bunce <Tim(dot)Bunce(at)pobox(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Garick Hamlin <ghamlin(at)isc(dot)upenn(dot)edu>, Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Status of plperl inter-sp calling
Date: 2010-01-07 07:37:15
Message-ID: 46D2D74F-A595-4D2D-A337-AE60D52A3DD1@kineticode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Jan 6, 2010, at 5:46 PM, Tom Lane wrote:

> I went with 5.8 as the cutoff, for a couple of reasons: we're not in
> the business of telling people they ought to be up-to-date, but only of
> rejecting versions that demonstrably fail badly; and I found out that
> older versions of awk are not sufficiently competent with && and || to
> code a more complex test properly :-(. A version check that doesn't
> actually do what it claims to is worse than useless, and old buggy awk
> is exactly what you'd expect to find on a box with old buggy perl.

Yes, but even a buggy old Perl is quite competent with && and ||. Why use awk to test the version of Perl when you have this other nice utility to do the job?

> (It's also worth noting that the perl version seen at configure time
> is not necessarily that seen at runtime, anyway, so there's not a lot
> of point in getting too finicky here.)

Fair enough.

Best,

David

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Stefan Kaltenbrunner 2010-01-07 07:54:34 Re: unresolved bugs
Previous Message Peter Eisentraut 2010-01-07 06:40:54 Re: unresolved bugs