ShmoopTube

00:00

Thank you We sneak And here's your shmoop du jour

00:05

brought to you by forced to fly Certainly not something

00:10

you want to hear your pilot complaining about as you

00:11

prepare for takeoff All right what are valid reasons for

00:15

choosing to create Forced to fly as an interface class

00:19

is dead of an abstract flack gnarly near your pencil

00:24

answered All right well it's thing option one seems like

00:30

a valid choice if objects other than animals were to

00:33

fly while the fly method would be different so we

00:36

can't implement the method because it would be unique for

00:39

different objects Well there's also clears option two If we

00:43

declared the method in an abstract class and implemented it

00:48

it would be the same across all club crashed up

00:51

Option three is also correct because you can't make sub

00:53

classes of interfaces but you can with abstract class that

00:58

work But if the programmer thought no sub classes would

01:01

be necessary an abstract class wouldn't be necessary Yeah well

01:06

although you claim that abstract classes aren't necessary jackson pollock 00:01:10.278 --> [endTime] uh might argue with you

Full Transcript