Front page | perl.perl5.porters |
Postings from June 2020
Re: Announcing Perl 7
Thread Previous
|
Thread Next
From:
Darren Duncan
Date:
June 30, 2020 05:33
Subject:
Re: Announcing Perl 7
Message ID:
d5bf902d-8f2e-6565-0955-131876757340@darrenduncan.net
On 2020-06-29 10:22 p.m., Tom Molesworth via perl5-porters wrote:
>
> On Tue, 30 Jun 2020 at 12:40, Darren Duncan wrote:
>
> 2. I also completely agree that IF Perl code lacks an explicit version marker,
> then a v7+ Perl interpreter should indeed interpret it as the latest version of
> Perl it understands implicitly, rather than interpreting it as Perl 5.0.0.
>
> So one concern that does not seem to have been addressed by the "enable by
> default" proposal is "what about CPAN". It used to be a selling point for Perl,
> would be a shame to lose that.
Well I DID say that CPAN is one of those places where explicit versions SHOULD
be used. And if any don't, well CPAN is public, and as you demonstrated we can
see what would break. And so we now are in the position to fix those modules.
> Note that we can't start with `use strict`, because many of the core modules
> would fail with that in force. I suspect it's also not a complete list of the
> proposed v7 directives. The main failure with this example (List::UtilsBy) is
> related to signatures - but I would suggest that testing it out on the
> dependencies that you're using in real code, seems that would give useful data
> points for the discussion?
Well the Perl core certainly should be dogfooding this. Whatever decision is
made should apply the same to the core, and if the core needs updating for
compatibility, then it gets updated before v7 of the interpreter is released.
A key pre-condition for Perl 7+ being released publicly is that both its bundled
core modules are compatible and also the most heavily used and most upriver
parts of CPAN are compatible, and the greater fraction the better.
-- Darren Duncan
Thread Previous
|
Thread Next