ACM Home Page
Please provide us with feedback. Feedback
Polymorphic panelists
Full text PdfPdf (134 KB)
Source Technical Symposium on Computer Science Education archive
Proceedings of the thirty-second SIGCSE technical symposium on Computer Science Education table of contents
Charlotte, North Carolina, United States
Pages: 410 - 411  
Year of Publication: 2001
ISBN:1-58113-329-4
Also published in ...
Authors
Byron Weber Becker  University of Waterloo, Waterloo, Ontario, Canada N2L 3G1
Richard Rasala  College of Computer Science, Northeastern University, Boston, MA
Joseph Bergin  Pace University, One Pace Plaza, NY
Christine Shannon  Centre College, Danville, KY
Eugene Wallingford  University of Northern Iowa, Cedar Falls, IA
Sponsor
SIGCSE: ACM Special Interest Group on Computer Science Education
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 5,   Downloads (12 Months): 11,   Citation Count: 0
Additional Information:

abstract   index terms   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/364447.364795
What is a DOI?

ABSTRACT

Polymorphism is an important object-oriented programming concept in which objects from two or more different classes respond to the same set of messages. For instance, HourlyEmployee, SalariedEmployee, and ContractEmployee all respond to the message calculatePay(). Instances of each class "do the right thing" to calculate their pay even though the methods to do so may be quite different. But the payroll program using these classes doesn't care - it can ask each object for the amount owed without caring what kind of employee it represents or how the amount is calculated.The panelists are all instances of subclasses of Professor which will respond to the following queries. Since each of the subclasses implement these queries differently, the answers will usually be different as well!• polymorphPreconditions(): The object (professor) specifies the information students must know before polymorphism is introduced in their class.• polymorphPresentation(): The object (professor) describes how polymorphism is introduced in their class.• polymorphStudentUsage(): The object (professor) describes how their students use polymorphism later in the course.• answerQuestions(): The object (professor) responds to any questions about their approach.


Collaborative Colleagues:
Byron Weber Becker: colleagues
Richard Rasala: colleagues
Joseph Bergin: colleagues
Christine Shannon: colleagues
Eugene Wallingford: colleagues