develooper Front page | perl.perl5.porters | Postings from July 2020

Re: Announcing Perl 7 Perl5 Porters <perl5-porters@perl.org>

Thread Previous | Thread Next
From:
Dan Book
Date:
July 1, 2020 14:12
Subject:
Re: Announcing Perl 7 Perl5 Porters <perl5-porters@perl.org>
Message ID:
CABMkAVU+EADM06AJCbFkbRM=5GXfe9rDCp7oHXoHuZnZKOouUg@mail.gmail.com
On Wed, Jul 1, 2020 at 8:37 AM Todd Rinaldo <toddr@cpanel.net> wrote:

>
>
> > On Jul 1, 2020, at 6:56 AM, Kent Fredric <kentfredric@gmail.com> wrote:
> >
> > On Wed, 1 Jul 2020 at 23:19, Salvador FandiƱo <sfandino@gmail.com>
> wrote:
> >> What I was trying to emphasize is that unless you explicitly declare the
> >> perl version semantics you want to use in some way (and I am
> >> definitively in the "use v7" camp here), your code would become broken
> >> in the next mayor release, if that follows an
> >> all-features-enabled-by-default policy.
> >
> > If this heads this way, I hope they have a provision in place for
> > "your code conflicts with a feature that will be enabled in perl ( $]
> > + 0.2 )" warnings like has been expected of the majority previous
> > backwards compatibility breaks.
> >
> > But that's ... probably going to be a *mountain* of fun to actually
> implement.
> >
>
> I think some tooling that ships with Perl and gives this advice or
> upgrades it would be very helpful. Potentially something that auto-upgraded
> would be nice.
>
> Example: Something that fixes indirect object notation automagically.
>

This is practically impossible. It's not even possible to statically detect
that indirect object notation is in use.

-Dan

Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About