> 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. ToddThread Previous | Thread Next