see feature*_enabled checks demonstrated in Re^5: Try::Tiny and -E and Re^7: Try::Tiny and -E
Try::Tiny can check either inside import() or die/skip right at the beginning of the module.
NB: you can provide a caller level to this routines.
> If you perform the check as these wrong times,
What should be the benefit of Try::Tiny exporting it's subs while feature-try is enabled?
In theory you could no feature "try" later in a sub-scope to re-enable those exports, but that's a very convoluted edge-case.
And I was mostly talking about "warning", warnings can be disabled if this convoluted edge-case is warranted.
Looking forward to your counter-examples!
Cheers Rolf
(addicted to the Perl Programming Language :)
see Wikisyntax for the Monastery
In reply to Re^13: Try::Tiny and -E
by LanX
in thread Try::Tiny and -E
by 1nickt
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |