It wasn't pasted. The really important word in the snippet which you quoted is "partly". Most of it is now non-experimental and can be used in long-term code with confidence. The only part which remains experimental for now is the finally {} block.

As of Perl 5.40, use of this feature without a finally block no longer triggers a warning. The optional finally block is still considered experimental and emits a warning, except when explicitly disabled as above.

I'm more than happy for p5p or PSC or whoever it is that decides these things to take their time with new features like this. Especially given the mess that was smartmatch and given/when. Nobody wants to see a repeat of that.

I'm more than happy for p5p or PSC or whoever it is that decides these things to take their time with new features like this. Especially given the mess that was smartmatch and given/when. Nobody wants to see a repeat of that.

Me too.

As mentioned earlier, warning lists that "try" feature could be removed. If that does not apply to whole of it, then it ought to be more specific. If it does or if "finally" is used, then "try" use ought to continue to spit out feature-is-experimental-warning.

I put a huge effort into writing New built-in perl5.38 try/catch syntax a year ago and was flabbergasted when it received zero responses. None. Very rare in my experience at PM. So thankyou parv and hippo for finally responding to my lonely little node, you just made my day. :-)

Further to hippo's excellent clarifying response, please note that I've further updated the Recent Features section of the newer Re: 5.40 released (perl new feature References) -- which BTW has always predicted that the finally block warning will finally disappear in perl v5.42. I hope to see that prediction fulfilled when perl v5.42 is finally released. :-)

👁️🍾👍🦟