encoding.pm has a Filter option which, instead of hooking the upgrad- ing of strings, simply runs the source of the file through a decoding source filter and does an effective 'use utf8'. This option actually makes sense and follows a sane model. Currently encoding.pm emits a deprecation warning on any ->import. Should it perhaps only emit such a warning when using ${^ENCODING}? It is the latter, after all, which we are trying to removed, because of the problems it causes.Thread Next