Re^4: 'finally' block in Perl?

Ah right, because the original question wanted to support multiple return places. Thank you for the detailed reply! I also realized that the first reply called it a "bare block" which I could have used to do a Google search had I read it more carefully. I found this when looking for a way to handle clean-up in a function that may exit early due to an exception, not a return. In my case, the "eval" approach (without the bare block) with a "die $@ if $@" is satisfactory so I don't have to pull in an extra dependency. Hypothetically, the "early return" case can be handled by wrapping early-returnable logic in a separate function, though I can see that this may be cumbersome in some contexts.

Comment on Re^4: 'finally' block in Perl?

Replies are listed 'Best First'.
Re^5: 'finally' block in Perl? by haukex (Archbishop) on Jan 08, 2019 at 16:46 UTC
die $@ if $@ Be careful with that, see Bug in eval in pre-5.14 - the better pattern is `eval { ...; 1 } or do { handle_error() };` Hypothetically, the "early return" case can be handled by wrapping early-returnable logic in a separate function, though I can see that this may be cumbersome in some contexts. There are several different ways to handle a kind of "return early but perform cleanup" in Perl, which one is most applicable depends on the situation (e.g. simple control flow, as you said using a separate function, the code shown in this thread, `finally` from a module like Try::Tiny, End, ...). If I were to use the bare block with last method, personally I'd prefer to label the block to make it absolutely clear where the `last` will jump to, and make it immune to accidentally adding in another bare block: `{ print "A\n"; FOO: { print "B\n"; { last FOO; print "C\n"; } print "D\n"; } # last jumps here print "E\n"; }` [download]	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re^5: 'finally' block in Perl?
by haukex (Archbishop) on Jan 08, 2019 at 16:46 UTC

die $@ if $@

Be careful with that, see Bug in eval in pre-5.14 - the better pattern is eval { ...; 1 } or do { handle_error() };

Hypothetically, the "early return" case can be handled by wrapping early-returnable logic in a separate function, though I can see that this may be cumbersome in some contexts.

There are several different ways to handle a kind of "return early but perform cleanup" in Perl, which one is most applicable depends on the situation (e.g. simple control flow, as you said using a separate function, the code shown in this thread, finally from a module like Try::Tiny, End, ...). If I were to use the bare block with last method, personally I'd prefer to label the block to make it absolutely clear where the last will jump to, and make it immune to accidentally adding in another bare block:

{
    print "A\n";
    FOO: {
        print "B\n";
        {
            last FOO;
            print "C\n";
        }
        print "D\n";
    }  # last jumps here
    print "E\n";
}
[download]

[reply]
[d/l]
[select]