Re^4: eval: Why use the 'Zombie error' idiom?

The reason I avoid Try::Tiny is that its catch block is actually a function in disguise, not just a block like with the original eval idiom. So a return from a Try::Tiny catch block returns just from that block, and not from the enclosing function, which is useless and misleading.

Comment on Re^4: eval: Why use the 'Zombie error' idiom?

Replies are listed 'Best First'.
Re^5: eval: Why use the 'Zombie error' idiom? by hippo (Archbishop) on Oct 18, 2019 at 13:15 UTC
Indeed so, and the Try::Tiny POD explains this in some detail. If you want to return directly from a `catch` block then Syntax::Keyword::Try might be for you? There's also TryCatch but that uses Moose so isn't exactly the lightest tool in the box.	[reply] [d/l]
Re^5: eval: Why use the 'Zombie error' idiom? by jcb (Parson) on Oct 18, 2019 at 23:13 UTC
Interestingly, the block names used with the loop control operators are dynamically scoped, so `last`, `next`, and `redo` all work in that context, but I do not think that there is any good way to actually return a value from the sub in such a block.	[reply] [d/l] [select]