Re: error message diff with Perl 5.22.0

From: Alex Hunsaker <badalex(at)gmail(dot)com>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: error message diff with Perl 5.22.0
Date: 2015-07-02 01:34:30
Message-ID: CAFaPBrTsgKYHKb+Wf=xK8shG7+=F2ty-OxEJdkq9wT_Jknj8-g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Jun 6, 2015 at 7:03 PM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:

> With the recently released Perl 5.22.0, the tests fail thus:
>
> -ERROR: Global symbol "$global" requires explicit package name at line 3.
> -Global symbol "$other_global" requires explicit package name at line 4.
> +ERROR: Global symbol "$global" requires explicit package name (did you
> forget to declare "my $global"?) at line 3.
> +Global symbol "$other_global" requires explicit package name (did you
> forget to declare "my $other_global"?) at line 4.
> CONTEXT: compilation of PL/Perl function "uses_global"
>
>
FWIW the committed expected file seems fine to me. There is not a perl
option to toggle this behavior (and even if there was, I think the
resulting changes to pl/perl functions we be quite ugly).

(What about the back branches? :D)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2015-07-02 01:37:26 Re: Expending the use of xlog_internal.h's macros
Previous Message Amit Kapila 2015-07-02 00:58:20 Re: drop/truncate table sucks for large values of shared buffers