Re^4: canonical doc explaing need for "eval { ... } or do {...}" construct

in reply to Re^3: canonical doc explaing need for "eval { ... } or do {...}" construct
in thread canonical doc explaing need for "eval { ... } or do {...}" construct

> Especially since Perl is getting a try keyword...

which is naturally not backwards compatible

Cheers Rolf
_{(addicted to the Perl Programming Language :)

Wikisyntax for the Monastery}

Comment on Re^4: canonical doc explaing need for "eval { ... } or do {...}" construct

Replies are listed 'Best First'.
Re^5: canonical doc explaing need for "eval { ... } or do {...}" construct by ikegami (Patriarch) on May 13, 2022 at 05:19 UTC
Quite the opposite. It's not any less backward compatible than creating a new module that exports `try`, seeing as you have to "import" it before you can use it.	[reply] [d/l]
Re^6: canonical doc explaing need for "eval { ... } or do {...}" construct by LanX (Saint) on May 13, 2022 at 06:20 UTC
I disagree since Try::Tiny is available for older versions, so importing will work "backwards" Cheers Rolf _{(addicted to the Perl Programming Language :) Wikisyntax for the Monastery}	[reply]
Re^7: canonical doc explaing need for "eval { ... } or do {...}" construct by ikegami (Patriarch) on May 13, 2022 at 17:31 UTC
I think you're saying that since the new keyword won't work on older versions, that it's not backwards compatible? That's not what backwards compatibility means. Backwards compatibility is the ability to continue to use existing code as-is. The new feature won't change that. Try::Tiny and its users will continue to work perfectly fine, so the feature is backwards compatible.	[reply]
Re^8: canonical doc explaing need for "eval { ... } or do {...}" construct by LanX (Saint) on May 13, 2022 at 19:59 UTC

In Section Seekers of Perl Wisdom