summaryrefslogtreecommitdiff
path: root/ext
diff options
context:
space:
mode:
authorFather Chrysostomos <sprout@cpan.org>2011-10-29 19:56:18 -0700
committerFather Chrysostomos <sprout@cpan.org>2011-11-06 01:13:46 -0700
commitf1c31c527b5fd97a0d6c39c815e40a37674881ca (patch)
tree35237861fdc41cd644f21efaf6f146c3cfc0d54c /ext
parentcc7b5b23f454a503cb20d27859ae5c49d0a911e3 (diff)
downloadperl-f1c31c527b5fd97a0d6c39c815e40a37674881ca.tar.gz
Forbid source filters in Unicode evals
Source filters have always been byte-level filters. Therefore they don’t make sense on Unicode strings, unless we are planning to add new APIs to support it. Until then, croak.
Diffstat (limited to 'ext')
-rw-r--r--ext/XS-APItest/t/eval-filter.t11
1 files changed, 10 insertions, 1 deletions
diff --git a/ext/XS-APItest/t/eval-filter.t b/ext/XS-APItest/t/eval-filter.t
index 8d370e59a7..d4a9153613 100644
--- a/ext/XS-APItest/t/eval-filter.t
+++ b/ext/XS-APItest/t/eval-filter.t
@@ -1,9 +1,18 @@
#!perl -w
use strict;
-use Test::More tests => 1;
+use Test::More tests => 3;
use XS::APItest;
+{
+ use feature "unicode_eval";
+ my $unfiltered_foo = "foo";
+ eval "BEGIN { filter() }";
+ like $@, qr/^Source filters apply only to byte streams at /,
+ 'filters die under unicode_eval';
+ is "foo", $unfiltered_foo, 'filters leak not out of unicode evals';
+}
+
BEGIN { eval "BEGIN{ filter() }" }
is "foo", "fee", "evals share filters with the currently compiling scope";