Re: cpan perl module - plperlu danger? - Mailing list pgsql-general

From merlyn@stonehenge.com (Randal L. Schwartz)
Subject Re: cpan perl module - plperlu danger?
Date
Msg-id 86fyhx1bp8.fsf@blue.stonehenge.com
Whole thread Raw
In response to Re: cpan perl module - plperlu danger?  ("A.M." <agentm@themactionfaction.com>)
List pgsql-general
>>>>> "A" == A M <agentm@themactionfaction.com> writes:

A>  [But even Safe.pm has had
A> dozens of bugs revealed over the years- caveat emptor.]

Eeeh?  Proof please? That's just FUD-raking.

From what I recall, there have been a few clever leakages that have been fixed
rather rapidly.

"few" ne "dozens".

The main problem with Safe is that it's at the wrong granularity (per opcode,
not per semantic operation).

But let's not be throwing the baby out with the bathwater... Safe is 99.97% of
the way there.

--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!

pgsql-general by date:

Previous
From: Richard Broersma Jr
Date:
Subject: Re: OLEDB Provider for Postgres
Next
From: "Relyea, Mike"
Date:
Subject: Re: Out of memory error in 8.1.0 Win32