Front page | perl.perl5.porters |
Postings from June 2020
Re: Announcing Perl 7
Thread Previous
|
Thread Next
From:
Dan Book
Date:
June 27, 2020 18:36
Subject:
Re: Announcing Perl 7
Message ID:
CABMkAVXP0C2wyTdZMuKCTux-9Cv-cWYLGDmbRrS-Vg9kJ06AHQ@mail.gmail.com
On Sat, Jun 27, 2020 at 12:46 PM Dan Book <grinnz@gmail.com> wrote:
> To summarize my overall point: I do not think that changing the default
> enabled features sufficiently solves the stated problems, to justify the
> amount of effort it will take to overcome the breakage it will introduce,
> when compared with an improved "use v7" which does not introduce any
> breakage and solves these problems as well.
>
To add one more data point for practical impact: Currently the way feature
bundles and "use VERSION" work is extremely helpful for oneliners. "use
VERSION" applies a set of features via a feature bundle, but separately
applies "use strict" - this is *not* part of the feature bundle. This
allows `perl -E` to apply the most current feature bundle, without enabling
strict. For the most part, the features in feature bundles have little or
no impact on common oneliners, so are largely beneficial - greatly
disproportionate from the impact they would have on the average CPAN or
in-house module, and moreso the average script. But strict breaks the
majority of common oneliners, which is of course easy for the user to fix
if they understand the problem, but also is proportionately less valuable
to oneliners.
Could a mechanism be designed and implemented so that oneliners still do
not enable strict and warnings by default? Of course, but this mechanism
already exists: the distinction between feature bundles and "use VERSION"
handles this different need.
-Dan
Thread Previous
|
Thread Next