Front page | perl.perl5.porters |
Postings from March 2023
On Fri, 21 Oct 2022 at 18:09, Ricardo Signes <perl.p5p@rjbs.manxome.org> wrote: > Deprecation and smartmatch: It will just use normal deprecation warning. Slated removal, v5.42. BooK will update his PR. > We found a few other things of "deprecated" type in perldiag to deal with: > > "use of goto to jump inward" should be fatal > "dot no longer in @INC in do" should stop warning I don't agree with this, and I think there should have been a broader discussion about this subject with the community before it was made and therefore I request that this be reopened for further review and wider discussion. I also believe that I am not alone in this opinion, although those opinions have been expressed to me privately I hope that those who share my view will speak up. I believe that there many good reasons to have deprecation sub-categories, and I have prepared https://github.com/Perl/perl5/pull/20916 to demonstrate the value that can be provided by supporting deprecation subcategories, to test them and to test our documentation of them, and generally improve how we handle them overall. I believe that this PR demonstrates that there is indeed value in having deprecation subcategories, and that we are missing useful opportunities for managing our deprecations that are made easy by having subcategories and difficult by not having them. IMO we should ONLY use subcategories for deprecations going forward, and should essentially deprecate the use of the broad category in our internal logic. The PR includes tests for this and multiple other aspects of the deprecation logic (for instance changes to diag.t to parse deprecate() macros), along with documentation improvements and fixes. cheers, YvesThread Previous | Thread Next