Just imagine, you are asked to enter your gmail Id and Password to login to your Gmail account. But, by mistake you have entered a wrong password. And what if, Gmail exits without giving you a second chance to enter the Password? - It is not acceptable.
Same thing applies for any application. We are allowed to make some sort of mistakes. So that we get a second chance to rectify that. Such mistakes in Kotlin are called as Exceptions.
So, the Exceptions should be handled/caught at runtime, and also the entire application should not close due to that Exception.
It is same as your Gmail account doesn't close when someone types a wrong password and at the same time Gmail needs to keep a track on how many times the user is entering a wrong Password.
Say for example, you have written a program to divide two numbers then add them. But by mistake, you tried to divide the number by zero.
Let us see what happens in the below example.
fun main(){ var x = 3 var y = 0 var z = x / y println("The divided result is "+z) var k = x + y println("The added result is "+k) }
So, if you see the above example, we have declared two variables x and y and initialised 3 and 0 to them.
var x = 3 var y = 0
Then we tried dividing them,
var z = x / y
And since, we tried to divide 3 by 0. It ended up with an error.
Exception in thread "main" java.lang.ArithmeticException: / by zero
That could be ok. But the problem is, the addition operation was not performed for the above error.
var k = x + y println("The added result is "+k)
And the program got halted. Which is not acceptable.
And Kotlin provides a solution to the above problem, with something called as a try - catch block.
So, in the try block, you can place the code if you suspect it might throw error.
And in the catch block, you can handle the error. Only if there is an error, the except block executes.
Now, all you need to do is, place the division operation inside the blocks of try. And if you want to display some message for that error, you can place the message in the catch block.
Now, let's modify the above code using try - catch block.
fun main(){ var x = 3 var y = 0 try { var z = x / y println("The divided result is "+z) } catch (ee: Exception) { println("The division couldn't be performed due to an error.") } var k = x + y println("The added result is "+k) }
Now, if you see the above output, it proceeded without any error. So, let us see how it worked.
So, in the above code, we have placed the division operation inside the try block.
try { var z = x / y println("The divided result is "+z) }
And as usual an error occurred because we wanted to divide the number by 0.
And luckily, the try block, handled the error. And the control comes to the except block.
catch (ee: Exception) { println("The division couldn't be performed due to an error.") }
And prints the output.
The division couldn't be performed due to an error.
And most importantly, the addition operation didn't get halted. And the below line executes, adding two numbers.
var k = x + y println("The added result is "+k)
Now, let us say, irrespective of any error. You want to display a message.
And Kotlin provides a finally block for that.
The finally block gets executed irrespective of any error.
Let us see the below example, where there is no error.
import java.lang.Exception fun main() { var x = 3 var y = 3 try { var z = x / y println("The divided result is "+ z) } catch (e: Exception) { println("The division couldn't be performed due to an error.") } finally { println("try block ended") } }
So, in the above program, there is no error. And the finally block got executed.
finally { println("try block ended") }
Now, let us say the below program has a division error.
import java.lang.Exception fun main() { var x = 3 var y = 0 try { var z = x / y println("The divided result is "+ z) } catch (e: Exception) { println("The division couldn't be performed due to an error.") } finally { println("try block ended") } }
So, the finally block gets executed, whether there is an error or not.