Finally block behavior in Kotlin - Step-by-Step Execution

Concept Flow - Finally block behavior

Try block starts

↓

Exception?

Yes→Catch block

↓

Catch block ends

↓

Try block ends

↓

Finally block

↓

Code after try-catch-finally

The finally block runs after try and catch blocks, no matter if an exception occurred or not.

Execution Sample

Kotlin

fun test() {
  try {
    println("Try block")
  } catch (e: Exception) {
    println("Catch block")
  } finally {
    println("Finally block")
  }
}

This code prints messages from try, catch (if exception), and finally blocks always.

Execution Table

Step	Action	Exception Thrown?	Block Executed	Output
1	Enter try block	No	Try	Try block
2	Try block completes	No	Try
3	No exception, skip catch	No	Catch skipped
4	Execute finally block	No	Finally	Finally block
5	Exit function	No	End

💡 Try block finishes without exception, finally block runs, then function ends.

Variable Tracker

Variable	Start	After Step 1	After Step 4	Final
exceptionThrown	false	false	false	false

Key Moments - 3 Insights

Does the finally block run if there is no exception?

Yes, as shown in execution_table step 4, finally runs even when no exception occurs.

What happens if an exception is thrown in the try block?

The catch block runs first to handle it, then finally runs. This is shown in the flow diagram.

Can finally block change the return value or throw another exception?

Yes, finally runs last and can override return or throw new exceptions, but this example shows normal flow.

Visual Quiz - 3 Questions

Look at the execution_table, which step shows the finally block running?

A Step 3

B Step 2

C Step 4

D Step 1

💡 Hint

Check the 'Block Executed' column for 'Finally' in execution_table row Step 4.

At which step does the program skip the catch block?

A Step 3

B Step 1

C Step 4

D Step 5

💡 Hint

Look at the 'Block Executed' column in execution_table where it says 'Catch skipped'.

If an exception was thrown in the try block, which block would run immediately after?

A Finally block

B Catch block

C Try block again

D Function ends immediately

💡 Hint

Refer to the concept_flow diagram showing exception path from try to catch.

Concept Snapshot

try { ... } catch(e) { ... } finally { ... }
- finally always runs after try and catch
- runs even if no exception occurs
- can override return or throw new exceptions
- used for cleanup like closing files or releasing resources

Full Transcript

In Kotlin, the finally block runs after the try and catch blocks no matter what. If the try block runs without errors, the catch block is skipped, but finally still runs. If an exception happens, the catch block runs first, then finally. This ensures cleanup code always executes. The example code prints messages from try, catch (if needed), and finally blocks. The execution table shows step-by-step which block runs and when. Variables track if an exception occurred. Key moments clarify that finally runs always, even without exceptions, and can affect return values or throw new exceptions. The quiz tests understanding of when finally runs and the order of blocks during exceptions.