لینک دانلود و خرید پایین توضیحات
دسته بندی : پاورپوینت
نوع فایل : .ppt ( قابل ویرایش و آماده پرینت )
تعداد اسلاید : 41 اسلاید
قسمتی از متن .ppt :
Programming in Java Lecture 4OOP Inheritance, Abstract classes, Interfaces
Ahmed Khademzadeh
khademzadeh@mshdiau.ac.ir
Azad University of Mashhad
(Lecture powerpoint slides provided by Manu Kumar - Stanford University)
Copyright © 2003, Manu Kumar
Recap
Last time
Java Collections
Iterators
ArrayList example
OOP
Inheritance
Overriding
Polymorphism
“Pop-down” rule
Downcasting
Grad example
Copyright © 2003, Manu Kumar
Today
Continue with OOP/Inheritance
Pop-down rule
Constructors
instanceOf
Grad example
Abstract superclasses
Account example
Java Interfaces
Moodable example
Today or next time
Start Drawing/GUI
Copyright © 2003, Manu Kumar
“Pop-Down” rule
The reciever knows it’s class
The flow of control jumps around different classes
No matter where there code is executing the receiver knows its class and does the messagemethod mapping correctly for each message!
Example
Receiver is the subclass (Grad), executing a method in the superclass(Student)
A message send that Grad overrides will “pop-down” to the Grad definition as in the case of getStress() )
لینک دانلود و خرید پایین توضیحات
دسته بندی : پاورپوینت
نوع فایل : .ppt ( قابل ویرایش و آماده پرینت )
تعداد اسلاید : 41 اسلاید
قسمتی از متن .ppt :
Programming in Java Lecture 4OOP Inheritance, Abstract classes, Interfaces
Ahmed Khademzadeh
khademzadeh@mshdiau.ac.ir
Azad University of Mashhad
(Lecture powerpoint slides provided by Manu Kumar - Stanford University)
Copyright © 2003, Manu Kumar
Recap
Last time
Java Collections
Iterators
ArrayList example
OOP
Inheritance
Overriding
Polymorphism
“Pop-down” rule
Downcasting
Grad example
Copyright © 2003, Manu Kumar
Today
Continue with OOP/Inheritance
Pop-down rule
Constructors
instanceOf
Grad example
Abstract superclasses
Account example
Java Interfaces
Moodable example
Today or next time
Start Drawing/GUI
Copyright © 2003, Manu Kumar
“Pop-Down” rule
The reciever knows it’s class
The flow of control jumps around different classes
No matter where there code is executing the receiver knows its class and does the messagemethod mapping correctly for each message!
Example
Receiver is the subclass (Grad), executing a method in the superclass(Student)
A message send that Grad overrides will “pop-down” to the Grad definition as in the case of getStress() )