Front page | perl.perl5.porters |
Postings from July 2020
Re: Perl 7 - updates
Thread Previous
|
Thread Next
From:
Leon Timmermans
Date:
July 5, 2020 10:52
Subject:
Re: Perl 7 - updates
Message ID:
CAHhgV8gsU-F-ZRHUKQ6C9TxKX6wTxGKDdGdis2C2kMNGtE0RdA@mail.gmail.com
On Sat, Jul 4, 2020 at 2:27 AM Todd Rinaldo <toddr@cpanel.net> wrote:
> > 2. Perl 5.xx continues to plod along, but in some 5.xx, `use v7`
> > starts to "work".
>
> Only maintenance releases of 5.32/5.30 happen for perl 5.
I believe we need at least a 5.34 release if we are going to sunset
perl5 for at least two reasons.
Firstly, that version really ought to install a perl5 binary by
default. And quite probably other modifications to facilitate perl5
and perl7 living next to each other, as per my previous email. It
should be able to live side-by-side with perl7 out-of-the-box.
Secondly, it makes no sense to sunset it with experimental features:
they're not going to change anymore, they should be unmarked.
Beyond that, it doesn't actually have to do much really (though
arguably we should update dual-life modules and unicode when
applicable).
> What I really kinda want for my own company's code base is 'use vl' (latest) or 'use vi' (infinity?) which would always choose all the new features of the coming major version. If that existed, our code would just set that and as we always do, adjust our code as we switch to a new version of Perl. Then we don't have to update 5000 files in our code base when we switch to Perl 8 or 9. But this is a wish list item. If we don't get this, we'll just do a big commit and move on ¯\_(ã)_/¯.
use latest?
Leon
Thread Previous
|
Thread Next