3 ms·
> The way Py2to3 migration was handled was also some abomination. Meanwhile if I need my Perl code to work like old Perl I just write use v5.10 in header... To
by cesarb 3y ago
> The way Py2to3 migration was handled was also some abomination. Meanwhile if I need my Perl code to work like old Perl I just write use v5.10 in header...
To be fair, the way the Perl 5 to Perl 6 migration was handled was worse. It got so bad that they ended up renaming Perl 6 to something else, after it had already been released under the Perl 6 name.
- ilyt 3y agoThere was no migration, it was just unfortunately named language
- theamk 3y agoSure there was, everyone was talking about perl6 migration back in 2000's. The "unfortunately named language" appeared once it became clear once migration failed. Here is one of the earliest announcements: https://www.perl.com/pub/2000/07/perl6.html/ https://www.perl.com/pub/2000/07/perl6.html/ .. some quotes: > So the upward migration path from Perl 5 to Perl 6 will probably be to run your code through a translator. > Larry promised not to abandon Perl 5. The 5.6 maintenance track will continue as planned, and the 5.7 development track will eventually yield Perl 5.8, as planned. 5.8 will be the final release of Perl 5, but it will continue to be maintained and stable. perl is at 5.37 now... so much for "5.8 will be the final release" :) Also, this does sounds awfully like Python 2->3 migration.