Front page | perl.perl5.porters |
Postings from March 2023
On Fri, 10 Mar 2023 18:49:14 +0000 "Paul \"LeoNerd\" Evans" <leonerd@leonerd.org.uk> wrote: > Now, all of the-above reasoning only justifies a ratchet that applies > at the version boundary when implicit lexical import of builtins > becomes a thing - that would be at least 5.39.1 and doesn't exist yet. > I remember that there was some reasoning why we also wanted that to > apply right the way back to 5.11, but it could be that the only reason > for that was related to the implict-vs-explicit "strict" bits change > that your other part of the PR undoes anyway. So perhaps we don't need > a ratchet point at the 5.11 boundary any more. Ahah. In fact, just as I re-read that back to myself I remembered something and dug out the original PR that added the warning. https://github.com/Perl/perl5/pull/19396 It indeed justifies this as: > This is because versions v5.11 or higher will enable the strictness > hints as if loaded by use strict, and earlier versions will clear > them. The model for this is complicated by the second set of > HINT_EXPLICIT_STRICT_* bits, which have now been decided are a bad > design and we'd like to remove them. So yes, it seems like that ratchet warning was only because of the explicit/implict strictness change, which your PR backs out anyway. So it seems we can move the warning in that case. But previous comment stands - we'd still like to keep the mechanism around, and just move its ratchet point to 5.39 instead (so in effect it doesn't happen yet, but keeping the code around for the future). -- Paul "LeoNerd" Evans leonerd@leonerd.org.uk | https://metacpan.org/author/PEVANS http://www.leonerd.org.uk/ | https://www.tindie.com/stores/leonerd/Thread Previous | Thread Next