Re: Miscellaneous changes to plperl [PATCH] - Mailing list pgsql-hackers

From Alex Hunsaker
Subject Re: Miscellaneous changes to plperl [PATCH]
Date
Msg-id 34d269d41001231740g1bedc1c3l47e29e1418432880@mail.gmail.com
Whole thread Raw
In response to Re: Miscellaneous changes to plperl [PATCH]  (Tim Bunce <Tim.Bunce@pobox.com>)
Responses Re: Miscellaneous changes to plperl [PATCH]
List pgsql-hackers
On Sat, Jan 23, 2010 at 16:16, Tim Bunce <Tim.Bunce@pobox.com> wrote:
> On Fri, Jan 22, 2010 at 08:59:10PM -0700, Alex Hunsaker wrote:
>> On Thu, Jan 14, 2010 at 09:07, Tim Bunce <Tim.Bunce@pobox.com> wrote:
>> I'd vote for use warnings; as well.
>
> I would to, but sadly it's not that simple.
>
> warnings uses Carp and Carp uses eval { ... } and, owing to a sad bug in
> perl < 5.11.4, Safe can't distinguish between eval "..." and eval {...}
> http://rt.perl.org/rt3/Ticket/Display.html?id=70970
> So trying to load warnings fails (at least for some versions of perl).

Well that stinks.

> I have a version of my final "Package namespace and Safe init cleanup
> for plperl" that works around that. I opted to post a less potentially
> controversial version of that patch in the end. If you think allowing
> plperl code to 'use warnings;' is important (and I'd tend to agree)
> then I'll update that final patch.

Sounds good.


pgsql-hackers by date:

Previous
From: Alex Hunsaker
Date:
Subject: Re: Miscellaneous changes to plperl [PATCH]
Next
From: Robert Haas
Date:
Subject: Re: restructuring "alter table" privilege checks (was: remove redundant ownership checks)