Front page | perl.perl5.porters |
Postings from July 2017
On Mon, Jul 03, 2017 at 01:03:37PM -0400, Sawyer X wrote: > > > On 07/01/2017 01:52 PM, Leon Timmermans wrote: > > On Sat, Jul 1, 2017 at 7:45 PM, <pali@cpan.org <mailto:pali@cpan.org>> > > wrote: > > > > On Saturday 01 July 2017 19:13:30 you wrote: > > > to break a decade and a half of software. > > > > Hm? What you mean with to break? Existing functions would still work, > > just there are also new functions under new names. Usage of old > > functions is just removed from documentation. > > > > > > Then I misunderstood your proposal, "rename" suggested to me that the > > old ones disappear. In that case I'm not sure I see the benefit of > > your proposal. Why would anyone want to use an interface that won't > > work on perls older than 5.28, and could disappear in a future version > > of perl (since that's the point of Internals::)? This isn't making > > sense to me. > > You could support it with Devel::PPPort. It's a simple addition. > > However, the problem remains that if someone were to use these new > functions without PPPort, their code would not work on older versions. I > can't see a way around that. These are perl functions (as documented in utf8.pm), not C functions, Devel::PPPort does nothing for us. The patch retains the old names, so that isn't an issue. But it does deprecate the old names, which is an issue, I can't imagine us removing these functions. As a side note, the original thread refers to: https://metacpan.org/source/SHAY/perl-5.24.1/cpan/Archive-Tar/lib/Archive/Tar.pm#L1501 which I could see as correct because of the way perl's unicode support (fails to) deal with filenames. TonyThread Previous | Thread Next