Re^6: Try::Tiny and -E

Any reason you didn't provide your tests? Because my testing confirms what I said.

$ perl -e'
   use feature qw( try );
   use Try::Tiny;
   try { };
   CORE::say "ok";
'
syntax error at -e line 4, near "};"
Execution of -e aborted due to compilation errors.
[download]

$ perl -e'
   use Try::Tiny;
   use feature qw( try );
   try { };
   CORE::say "ok";
'
syntax error at -e line 4, near "};"
Execution of -e aborted due to compilation errors.
[download]

And

$ perl -e'
   use feature qw( try );
   use Try::Tiny;
   { no feature qw( try ); try { }; }
   CORE::say "ok";
'
ok
[download]

$ perl -e'
   use Try::Tiny;
   use feature qw( try );
   { no feature qw( try ); try { }; }
   CORE::say "ok";
'
ok
[download]

So I repeat: The order in which they are loaded is irrelevant, and what matters is if the feature is enabled or not when the try is encountered.

Comment on Re^6: Try::Tiny and -E Select or Download Code

Replies are listed 'Best First'.
Re^7: Try::Tiny and -E by LanX (Saint) on Dec 29, 2025 at 11:56 UTC
I never doubted that `feature "try"` will dominate, regardless of the compilation order. I said that the order matters in attempting to warn about the conflict during import/activation. --> > I think Try::Tiny should attempt to warn you or die. In the OP's example Try::Tiny is activated first and can't know about a later feature. This case must be addressed by the features. Or more generally, only the second "change" can detect the first. FWIW: I started a discussion on Reddit while PM was unreachable: Perl's feature.pm and backwards incompatibility Cheers Rolf _{(addicted to the Perl Programming Language :) see Wikisyntax for the Monastery}	[reply] [d/l]
Re^8: Try::Tiny and -E by ikegami (Patriarch) on Dec 30, 2025 at 00:02 UTC
In the OP's example Try::Tiny is activated first and can't know about a later feature. I think it can check correctly, but I'm not sure. If it can, it can do so regardless of whether it was loaded first or not. And if it can, it's not trivial. More importantly, is it even its job? After all, the following doesn't warn: `sub print { ... } print ...;` [download] Maybe this is something Perl::Critic can handle.	[reply] [d/l]
Re^9: Try::Tiny and -E by LanX (Saint) on Dec 30, 2025 at 03:10 UTC
That's because `print` is a very special beast which allows an unusual `print FH @args` syntax. compare `~$ perl use warnings; sub shift {} shift; __END__ Ambiguous call resolved as CORE::shift(), qualify as such or use & at +- line 4. ~$` [download] Other languages like Javascript block the use of built-ins as function names. This could be a solution for the case `print` and similar commands. Cheers Rolf _{(addicted to the Perl Programming Language :) see Wikisyntax for the Monastery}	[reply] [d/l] [select]
Re^10: Try::Tiny and -E by ikegami (Patriarch) on Dec 30, 2025 at 05:06 UTC