1

00:00:08,110  -->  00:00:10,450
Hi there this is Needham under no no.

2

00:00:10,490  -->  00:00:11,890
And welcome back.

3

00:00:12,310  -->  00:00:16,660
So far we learned about writing good obdurately entered software.

4

00:00:16,660  -->  00:00:24,460
Now it's time to learn about how to make our software more robust and more reliable and the core exceptions

5

00:00:24,640  -->  00:00:26,100
is going to help us with that.

6

00:00:28,290  -->  00:00:35,040
Look at the motivation as professional programmers we all want our code to be as error free as possible

7

00:00:35,050  -->  00:00:35,270
.

8

00:00:36,080  -->  00:00:43,460
But despite all the wonderful read error free programs at run time with Mr. Lincoln there summers are

9

00:00:43,510  -->  00:00:50,920
normally such errors are exceptions rather than not that is to happen only in exceptional situations

10

00:00:52,420  -->  00:00:59,590
for example partnerships over the probates of of service might have gone on on our own database might

11

00:00:59,590  -->  00:01:07,300
have been done and these things are not in our control but good programmers would think about such exceptional

12

00:01:07,300  -->  00:01:10,250
situations and would write code to handle them.

13

00:01:11,840  -->  00:01:16,400
An example could be to automatically connect to an alternate partner solver.

14

00:01:16,460  -->  00:01:23,320
When one of them is found to be inaccessible so programmers writing some code to recover from such exceptional

15

00:01:23,320  -->  00:01:31,850
situations and this leads to a robust software them you've already fragile and exceptional situations

16

00:01:31,850  -->  00:01:39,280
happen things can break and it can bring trouble to both the organization as well as a programmer so

17

00:01:39,350  -->  00:01:41,240
you want to watch such things.

18

00:01:41,240  -->  00:01:47,680
And this chapter helps us in learning about tools for writing group or software not let's look at the

19

00:01:47,680  -->  00:01:48,590
agenda.

20

00:01:48,970  -->  00:01:55,450
So we're talking about exceptional situations when we encounter errors and in programming such exceptional

21

00:01:55,540  -->  00:01:59,830
issues are meaningfully referred to as exceptions.

22

00:01:59,830  -->  00:02:05,590
Exception is basically a language feature and when such exceptions happen we should also be able to

23

00:02:05,590  -->  00:02:13,010
handle them in some effective way so there must be some exception handling code to and this chapter

24

00:02:13,370  -->  00:02:20,460
is all about how exceptions can be represented on how they can behinder dystopic is so important that

25

00:02:20,550  -->  00:02:28,380
effective Dallow book has one entire chapter dedicated to exceptions NBP we learn almost all the recommendations

26

00:02:28,440  -->  00:02:30,450
prescribed in their chapter.

27

00:02:30,450  -->  00:02:37,160
It will be 8 or 9 items and we will also implement around half of them some writing a lot of courting

28

00:02:37,170  -->  00:02:45,630
this chapter finally be also discuss something called associates Well exceptions and the corresponding

29

00:02:45,630  -->  00:02:52,860
exception handling mechanism ensures suffers robustness assertions are useful to ensure that the software

30

00:02:52,860  -->  00:02:53,920
works correctly.

31

00:02:54,860  -->  00:02:59,660
Do gooder exhibitions on associations are useful for building reliable software.

32

00:03:00,140  -->  00:03:03,040
So let's go ahead and learn all about exceptions