Front page | perl.perl5.porters |
Postings from March 2023
On Mon, 20 Mar 2023 at 12:17, Paul "LeoNerd" Evans <leonerd@leonerd.org.uk> wrote: > On Mon, 20 Mar 2023 04:44:16 +0000 > Zefram via perl5-porters <perl5-porters@perl.org> wrote: > > > Paul "LeoNerd" Evans wrote: > > >Yes; that is exactly the point. We wanted it to have (what you call) > > >the "hard stricture" behaviour in 5.36. > > > > Whatever you wanted, "use v5.36" on actual Perl 5.36 actually exhibits > > soft stricture behaviour. That's the established meaning of "use > > v5.36", and to change it to hard stricture would be a break of > > backcompat. > > Ahyes; it seems my memory of this was wrong. I was remembering having > actually changed the behaviour, rather than simply having *intended* to > at some future time. > > The boundary should sit at 5.37, you're right. > > ... > > Perhaps you're seeing my patch as "fixing" and "reverting" these > > versions because you're seeing it as a replacement for some other > > patch, planned but never applied to blead, that would have changed > > the effects of those declarations? > > > > > https://github.com/Perl/perl5/pull/20944 > > > > The change of the stricture behaviour threshold from 5.37 to 5.35 > > would be a break of backcompat, and is a bad idea. > > Yes; I'll undo that second part. > Do you want this to be part of the 5.37.10 release? I havent started yet (just been reading the docs and getting myself prepped), so there is still time. cheers, Yves -- perl -Mre=debug -e "/just|another|perl|hacker/"Thread Previous | Thread Next