diff options
| author | Father Chrysostomos <sprout@cpan.org> | 2012-04-24 13:48:19 -0700 |
|---|---|---|
| committer | Father Chrysostomos <sprout@cpan.org> | 2012-05-21 16:51:36 -0700 |
| commit | 3d3d38d4e9515d9e6801cfd7976a3633dbfe12d2 (patch) | |
| tree | 874a4154afe8b67d8c25a9f0f7696ef46240aa05 /Porting | |
| parent | d9bad346a16eb87a6306ab3d32ca301cc10d1323 (diff) | |
| download | perl-3d3d38d4e9515d9e6801cfd7976a3633dbfe12d2.tar.gz | |
Remove todo for UTF8 source filters
Source filters don’t really make sense on character streams. They are
designed for streams of bytes coming straight from a file. Things
stop making sense if you have ‘use utf8’ in a UTF-8 scalar (does that
mean double-decode?).
It’s for this reason that evalbytes respects source filters, while
eval does not. (It doesn’t outside the unicode_eval feature, because
it was never really thought about and the implementation didn’t take
it into account, resulting in strange behaviour. It doesn’t with the
unicode_eval feature, because it was intentionally prohibited.)
Diffstat (limited to 'Porting')
| -rw-r--r-- | Porting/todo.pod | 9 |
1 files changed, 0 insertions, 9 deletions
diff --git a/Porting/todo.pod b/Porting/todo.pod index 6d2d51a5ba..43fb7a8d0c 100644 --- a/Porting/todo.pod +++ b/Porting/todo.pod @@ -878,15 +878,6 @@ was added, with the result that the synthetic start class often will fail to narrow down the possible choices when given non-Latin1 input. Karl Williamson has been working on this - talk to him. -=begin todo - -Many things are fixed, but is these still true? - - The tokeniser ignores the UTF-8-ness of C<PL_rsfp>, or any SVs - returned from source filters. - -=end - =head2 state variable initialization in list context Currently this is illegal: |