-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Just as a followup, I reported this as a bug and it is
being looked at and discussed:
http://rt.perl.org/rt3//Public/Bug/Display.html?id=47576
Appears there is no easy resolution yet.
- --
Greg Sabino Mullane [EMAIL PROTECTED]
PGP Key:
Greg Sabino Mullane wrote:
Just as a followup, I reported this as a bug and it is
being looked at and discussed:
http://rt.perl.org/rt3//Public/Bug/Display.html?id=47576
Appears there is no easy resolution yet.
We might be able to do something with the suggested workaround. I will
Andrew Dunstan wrote:
Greg Sabino Mullane wrote:
Just as a followup, I reported this as a bug and it is being looked
at and discussed:
http://rt.perl.org/rt3//Public/Bug/Display.html?id=47576
Appears there is no easy resolution yet.
We might be able to do something with the
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Ugh, in testing I see some nastiness here without any explicit
require. It looks like there's an implicit require if the text
contains certain chars.
Exactly.
Looks like it's going to be very hard, unless someone has some
brilliant
Greg Sabino Mullane wrote:
Ugh, in testing I see some nastiness here without any explicit
require. It looks like there's an implicit require if the text
contains certain chars.
Exactly.
Looks like it's going to be very hard, unless someone has some
brilliant insight I'm missing
Andrew Dunstan [EMAIL PROTECTED] writes:
I tried something like that briefly and it failed. The trouble is, I
think, that since the engine tries a require it fails on the op test
before it even looks to see if the module is already loaded.
I think we have little choice but to report this as
Greg Sabino Mullane wrote:
Yes, we might want to consider making utf8 come pre-loaded for plperl. There
is no direct or easy way to do it (we don't have finer-grained control than
the 'require' opcode), but we could probably dial back restrictions,
'use' it, and then reset the Safe
Andrew Dunstan wrote:
Greg Sabino Mullane wrote:
Yes, we might want to consider making utf8 come pre-loaded for
plperl. There is no direct or easy way to do it (we don't have
finer-grained control than the 'require' opcode), but we could
probably dial back restrictions, 'use' it, and
Andrew Dunstan wrote:
Ugh, in testing I see some nastiness here without any explicit
require. It looks like there's an implicit require if the text
contains certain chars. I'll see what I can do to fix the bug,
although I'm not sure if it's possible.
Looks like it's going to be very
