<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://wiki.expertiza.ncsu.edu/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Dcdulin</id>
	<title>Expertiza_Wiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://wiki.expertiza.ncsu.edu/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Dcdulin"/>
	<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=Special:Contributions/Dcdulin"/>
	<updated>2026-05-10T13:45:26Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.41.0</generator>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC_216_F09/polymorphism_showdown&amp;diff=29780</id>
		<title>CSC 216 F09/polymorphism showdown</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC_216_F09/polymorphism_showdown&amp;diff=29780"/>
		<updated>2009-11-19T20:44:55Z</updated>

		<summary type="html">&lt;p&gt;Dcdulin: /* Participants and Props */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Jim Creager and Davis Dulin'''&lt;br /&gt;
&lt;br /&gt;
==Polymorphism - Changing the Shape of Your Program==&lt;br /&gt;
&lt;br /&gt;
Polymorphism is the ability of a subclass to define new or share functionality with a superclass.  A subclass automatically has possession of public and protected variables and methods in its superclass.  These inherited variables and methods can be called directly from an object of the subclass without having to change type.  &lt;br /&gt;
&lt;br /&gt;
===Overriding===&lt;br /&gt;
It is also possible to redefine variables and methods within a subclass.  In such a case, a variable/method defined in the subclass '''overrides''' the variable/method with the same name in the superclass.  When called from an instance of the subclass, the variable/method defined in the subclass will be accessed instead of the one in the superclass.&lt;br /&gt;
&lt;br /&gt;
===Overloading===&lt;br /&gt;
'''Overloading''' is a technique by which a method takes on many forms.  Overloading occurs when a method name is used multiple times, but each instance of the method contains different parameters.  This allows multiple variations of the same action to occur depending on circumstances.&lt;br /&gt;
&lt;br /&gt;
===Casting===&lt;br /&gt;
Polymorphism also allows objects of one class to be transformed into objects of another class.  This is particularly useful when changing functionality in an inheritance relationship.  An instance of the superclass’ type can be set equal to an instance of the subclass’ type without any conflicts in the program.  This is because the subclass is a more specific class of the superclass.  Moving from subclass to superclass, however, would be making the subclass more generic.  A technique known as casting is required to perform this change.  '''Casting''' objects is only valid when moving in a upward along an object’s hierarchy (up to the superclass).  Casting cannot be used between objects on the same level of the object hierarchy, and casting is not necessary to move down the object hierarchy.  By placing a superclass’ name in parentheses just before the object you want to transform, you are declaring a new type, or casting.&lt;br /&gt;
&lt;br /&gt;
==Polymorphism Showdown - The Game==&lt;br /&gt;
&lt;br /&gt;
Polymorphism Showdown is a quiz-based game that tests knowledge of polymorphism concepts with relation to inheritance.  The goal is to familiarize participants with casting, overloading, and overriding.  Questions use a variety of formats, including UML diagrams and code snippets, to acclimate participants to conceptual application and direct code application.  Participants are required to think on their feet and answer quickly so that an active audience is maintained and learning continues.&lt;br /&gt;
&lt;br /&gt;
===Participants and Props===&lt;br /&gt;
Required:  [[http://www4.ncsu.edu/~dcdulin/ PowerPoint]] slideshow of quiz questions, [http://spreadsheets.google.com/viewform?formkey=dHRISWdoc290c0hPOEJRVG1NSXlvYVE6MA GoogleDocs answer form], [http://spreadsheets.google.com/ccc?key=ttHIghsotsHO8BQTmMIyoaQ corresponding GoogleDocs spreadsheet], and a chalkboard/whiteboard for score keeping.&lt;br /&gt;
&lt;br /&gt;
The entire class participates in this exercise.  Students attempt quiz problems as individuals while earning points for their team.  Rows compete against each other to earn the highest score.&lt;br /&gt;
&lt;br /&gt;
===How It Works===&lt;br /&gt;
There will be two types of questions in the game:  free-for-all and showdown.  Numbered questions indicate a free-for-all type in which all students participate.  Numbered questions followed by an ‘S’ indicate a showdown type in which select students participate.  All students attempt to correctly answer free-for-all problems as fast as possible.  The first student from each row to answer correctly advances to the showdown round as a representative for his/her row.  The first student to correctly answer the showdown problem receives a point for his/her row.  &lt;br /&gt;
&lt;br /&gt;
===Steps===&lt;br /&gt;
# The instructor should first create tally columns on the chalkboard/whiteboard for each row of students in the classroom.&lt;br /&gt;
# The instructor should then bring up the Polymorphism Showdown PowerPoint on the display.  The option is given on the home slide to review polymorphism concepts, review game instructions, or skip straight to the questions.&lt;br /&gt;
# When ready to begin the game, a link to the GoogleDoc answer form will need to be provided to the students.  At this time, the instructor should pull up the form’s corresponding spreadsheet on another computer or a second window.&lt;br /&gt;
# To begin the exercise, every student should fill in the next question number, his/her initials, and his/her row number on the GoogleDoc answer form.  The answer text field should be left blank, and the form should NOT yet be submitted.&lt;br /&gt;
# The instructor should then count down and flip the PowerPoint to the slide containing the next question.&lt;br /&gt;
# Students are to answer and submit the form as fast as possible.  Each student should only submit once.&lt;br /&gt;
# After 30 seconds, the instructor should prevent the spreadsheet from accepting submissions.  The PowerPoint can then be changed to the next slide which contains the answer.&lt;br /&gt;
# The instructor should then sort data in the spreadsheet by right clicking the “Row Number” column and selecting “From A-Z.”  This will organize answers into groups of row 1, row 2, etc., and answers within each group will be in order of time submitted (earliest first).&lt;br /&gt;
# The first person from each row to submit the correct answer (identified by initials) is then designated to participate in the next question, a showdown between rows.&lt;br /&gt;
# After designating the representatives for each row, the instructor should clear the data cells of the spreadsheet.  Submissions should be permitted once again.  This allows the same form and spreadsheet to be reused.&lt;br /&gt;
# Row representatives then revisit the GoogleDoc form and fill out entries as before, this time selecting the appropriate showdown question number.&lt;br /&gt;
# The instructor counts down and the PowerPoint is flipped to the next slide which contains the showdown question.&lt;br /&gt;
# Students are to answer and submit as fast as possible.&lt;br /&gt;
# Data will fill the spreadsheet in order of time submitted.  When the first correct answer arrives, the instructor should announce that there is a winner and stop further submissions from being received.&lt;br /&gt;
# The instructor then adds a tally to the chalkboard/whiteboard for the row that the winner represents.&lt;br /&gt;
# The instructor should clear the data cells of the spreadsheet.  Submissions should be permitted once again.  &lt;br /&gt;
# Steps 4-16 are repeated for remaining questions.&lt;/div&gt;</summary>
		<author><name>Dcdulin</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=PowerPoint&amp;diff=27972</id>
		<title>PowerPoint</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=PowerPoint&amp;diff=27972"/>
		<updated>2009-11-18T03:49:00Z</updated>

		<summary type="html">&lt;p&gt;Dcdulin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;THIS IS THE POWER POINT PRESENTATION IN TEXT FORM.  UNABLE TO LOAD THE POWER POINT ONTO WEB SPACE AT THE MOMENT.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Polymorphism Showdown&lt;br /&gt;
&lt;br /&gt;
Davis Dulin, &lt;br /&gt;
&lt;br /&gt;
James Creager, and Ian Charles&lt;br /&gt;
&lt;br /&gt;
Continue to Overview&lt;br /&gt;
&lt;br /&gt;
Skip to Instructions&lt;br /&gt;
&lt;br /&gt;
Skip to Questions&lt;br /&gt;
&lt;br /&gt;
Polymorphism &lt;br /&gt;
&lt;br /&gt;
Polymorphism is the ability of a subclass to define new or share functionality with a superclass.¬† A subclass automatically has possession of public and protected variables and methods in its superclass.¬† These inherited variables and methods can be called directly from an object of the subclass without having to change type.&lt;br /&gt;
&lt;br /&gt;
¬†&lt;br /&gt;
&lt;br /&gt;
Overriding&lt;br /&gt;
&lt;br /&gt;
It is also possible to redefine variables and methods within a subclass.¬† In such a case, a variable/method defined in the subclass overrides the variable/method with the same name in the superclass.¬† When called from an instance of the subclass, the variable/method defined in the subclass will be accessed instead of the one in the superclass.&lt;br /&gt;
&lt;br /&gt;
Overloading&lt;br /&gt;
&lt;br /&gt;
Overloading is a technique by which a method takes on many forms.¬† Overloading occurs when a method name is used multiple times, but each instance of the method contains different parameters.¬† This allows multiple variations of the same action to occur depending on circumstances.&lt;br /&gt;
&lt;br /&gt;
Casting&lt;br /&gt;
&lt;br /&gt;
Polymorphism also allows objects of one class to be transformed into objects of another class.¬† This is particularly useful when changing functionality in an inheritance relationship.¬† An instance of the superclass‚Äô type can be set equal to an instance of the subclass‚Äô type without any conflicts in the program.¬† This is because the subclass is a more specific class of the superclass.¬† Moving from subclass to superclass, however, would be making the subclass more generic. ¬†A technique known as casting is required to perform this change.¬†Casting objects is only valid when moving up an object‚Äôs hierarchy (up to the superclass).¬† Casting cannot be used between objects on the same level of the object hierarchy, and casting is not necessary to move down the object hierarchy. ¬†In order to cast, you place a superclass‚Äô name in parentheses just before the object you want to transform. By doing this, you are declaring a new type.&lt;br /&gt;
&lt;br /&gt;
How to Play&lt;br /&gt;
&lt;br /&gt;
Open the GoogleDoc form.¬† See instructor for web address.&lt;br /&gt;
&lt;br /&gt;
Fill out the form except for the answer blank.&lt;br /&gt;
&lt;br /&gt;
The instructor will change to the slide containing the question.&lt;br /&gt;
&lt;br /&gt;
Submit a correct answer in the form as quickly as possible.&lt;br /&gt;
&lt;br /&gt;
After 1min the instructor will call time, reveal the answer slide, and determine winners. &lt;br /&gt;
&lt;br /&gt;
¬†&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
How to Play&lt;br /&gt;
&lt;br /&gt;
Every numbered question has a showdown question (S) that follows.&lt;br /&gt;
&lt;br /&gt;
Points are only earned from showdown questions.&lt;br /&gt;
&lt;br /&gt;
Everyone competes in numbered questions.¬† Selected winners compete in showdown questions. &lt;br /&gt;
&lt;br /&gt;
How To Play&lt;br /&gt;
&lt;br /&gt;
For numbered questions:¬† The first person to provide a correct answer from each row in the classroom will advance to the showdown.¬† If a row does not submit a correct answer, no player advances from that row.&lt;br /&gt;
&lt;br /&gt;
¬†&lt;br /&gt;
&lt;br /&gt;
For showdown questions:¬† The first person to provide a correct answer earns a point for his/her row.¬† The instructor will tally the score on the board.&lt;br /&gt;
&lt;br /&gt;
¬†&lt;br /&gt;
&lt;br /&gt;
The row with the most points at the end of the questions wins. &lt;br /&gt;
&lt;br /&gt;
How To Play&lt;br /&gt;
&lt;br /&gt;
You may be asked to:&lt;br /&gt;
&lt;br /&gt;
identify something as legal or illegal&lt;br /&gt;
&lt;br /&gt;
write out variable declarations&lt;br /&gt;
&lt;br /&gt;
identify the type of polymorphism&lt;br /&gt;
&lt;br /&gt;
¬†&lt;br /&gt;
&lt;br /&gt;
NOTE: &amp;quot;illegal&amp;quot; may be the answer at any time For showdown questions:¬† The first person to provide a correct answer earns a point for his/her row.¬† The instructor will tally the score on the board.&lt;br /&gt;
&lt;br /&gt;
A slide demonstrating the layout follows.&lt;br /&gt;
&lt;br /&gt;
Question # and Category Will Be Here&lt;br /&gt;
&lt;br /&gt;
Question Will Be Here&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
If Included, Diagram Will Be Here&lt;br /&gt;
&lt;br /&gt;
Upcoming Question Will Be Here&lt;br /&gt;
&lt;br /&gt;
Question 1 follows.&lt;br /&gt;
&lt;br /&gt;
Q1 - Casting&lt;br /&gt;
&lt;br /&gt;
consider a class named Transportation, with subclasses named Bus, Car, and Bike. ¬†If you have an instance of Car created, how could you cast that Car instance to be of type Bus?&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Answer to Question 1 follows.&lt;br /&gt;
&lt;br /&gt;
Q1 - Answer&lt;br /&gt;
&lt;br /&gt;
illegal&lt;br /&gt;
&lt;br /&gt;
Question 1 Showdown follows.&lt;br /&gt;
&lt;br /&gt;
Q1S - &lt;br /&gt;
&lt;br /&gt;
ADDED SOME MORE.¬† TURNED OUT TO BE EASY SINCE REPETITIVE.¬† SHOULD SHOOT FOR 15.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
OK, SOUNDS GOOD&lt;br /&gt;
&lt;br /&gt;
Answer to Question 1 Showdown follows.&lt;br /&gt;
&lt;br /&gt;
Q1S - Answer&lt;br /&gt;
&lt;br /&gt;
¬†&lt;br /&gt;
&lt;br /&gt;
Question 2 follows.&lt;br /&gt;
&lt;br /&gt;
Q2 - Casting&lt;br /&gt;
&lt;br /&gt;
If BMW is a subclass of Car then how would you cast myCar, an instance of Car, to be of type BMW?&lt;br /&gt;
&lt;br /&gt;
answer:¬†myCar = (BMW) car&lt;br /&gt;
&lt;br /&gt;
Answer to Question 2 follows.&lt;br /&gt;
&lt;br /&gt;
Q2 - Answer&lt;br /&gt;
&lt;br /&gt;
¬†&lt;br /&gt;
&lt;br /&gt;
Question 2 Showdown follows.&lt;br /&gt;
&lt;br /&gt;
Q2S - &lt;br /&gt;
&lt;br /&gt;
¬†&lt;br /&gt;
&lt;br /&gt;
Answer to Question 2 Showdown follows.&lt;br /&gt;
&lt;br /&gt;
Q2S - Answer&lt;br /&gt;
&lt;br /&gt;
¬†&lt;br /&gt;
&lt;br /&gt;
Question 3 follows.&lt;br /&gt;
&lt;br /&gt;
Q3 - Casting&lt;br /&gt;
&lt;br /&gt;
An Animal superclass exists with subclasses Wolf and Gator.¬† Objects of each have been instantiated (a, w, and g respectively).¬† Which of the following is legal?&lt;br /&gt;
&lt;br /&gt;
¬†&lt;br /&gt;
&lt;br /&gt;
a)¬† w = (Wolf) g;&lt;br /&gt;
&lt;br /&gt;
b)¬† w = g;&lt;br /&gt;
&lt;br /&gt;
c)¬† a = g;&lt;br /&gt;
&lt;br /&gt;
d)¬† w = a;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Answer to Question 3 follows.&lt;br /&gt;
&lt;br /&gt;
Q3 - Answer&lt;br /&gt;
&lt;br /&gt;
c)¬† a = g;&lt;br /&gt;
&lt;br /&gt;
¬†&lt;br /&gt;
&lt;br /&gt;
No cast is necessary when moving down the object hierarchy. &lt;br /&gt;
&lt;br /&gt;
Question 3 Showdown follows.&lt;br /&gt;
&lt;br /&gt;
Q3S - Casting&lt;br /&gt;
&lt;br /&gt;
Following the same premise:¬† An Animal superclass exists with subclasses Wolf and Gator.¬† Objects of each have been instantiated (a, w, and g respectively). &lt;br /&gt;
&lt;br /&gt;
¬†&lt;br /&gt;
&lt;br /&gt;
Is the following legal?&lt;br /&gt;
&lt;br /&gt;
g = (Gator) a;&lt;br /&gt;
&lt;br /&gt;
Answer to Question 3 Showdown follows.&lt;br /&gt;
&lt;br /&gt;
Q3S - Answer&lt;br /&gt;
&lt;br /&gt;
yes&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
When moving up the object hierarchy, a cast is necessary.&lt;br /&gt;
&lt;br /&gt;
Question 4 follows.&lt;br /&gt;
&lt;br /&gt;
Q4 - Casting &lt;br /&gt;
&lt;br /&gt;
2) Given the UML diagram, how would you declare &amp;quot;athlete&amp;quot; of type Athlete as &amp;quot;sp&amp;quot; of type SoccerPlayer?&lt;br /&gt;
&lt;br /&gt;
Q4 - Answer&lt;br /&gt;
&lt;br /&gt;
athlete = sp;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
No cast is needed when moving down the object hierarchy.&lt;br /&gt;
&lt;br /&gt;
Q4S - Overriding&lt;br /&gt;
&lt;br /&gt;
SoccerPlayer and FootballPlayer both have a kick method, neither of which has a parameter.¬† Is this an example of overriding?&lt;br /&gt;
&lt;br /&gt;
Q4S - Answer&lt;br /&gt;
&lt;br /&gt;
no&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
The FootballPlayer class does not inherit a kick method to override.¬† The same applies to SoccerPlayer.&lt;br /&gt;
&lt;br /&gt;
Q5 - Overloading/Overriding&lt;br /&gt;
&lt;br /&gt;
Is this an example of overloading, overriding, both, or neither?¬† All methods in the diagram do not have parameters.&lt;br /&gt;
&lt;br /&gt;
Q5 - Answer&lt;br /&gt;
&lt;br /&gt;
overriding&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Transformer inherits shoot and move methods, but then defines its own.&lt;br /&gt;
&lt;br /&gt;
Q5S - Overloading&lt;br /&gt;
&lt;br /&gt;
In one line, define a method for the Transformer class that overloads shoot.¬† All methods in the diagram do not have parameters.&lt;br /&gt;
&lt;br /&gt;
Q5S - Answer&lt;br /&gt;
&lt;br /&gt;
___ void shoot( ___¬† ___ ){}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Any parameter will work because the previously defined method has no parameter.&lt;br /&gt;
&lt;br /&gt;
Override&lt;br /&gt;
&lt;br /&gt;
¬†&lt;br /&gt;
&lt;br /&gt;
Q5 - Inheritance&lt;br /&gt;
&lt;br /&gt;
Inheritance plays an important role with regards to the restrictions of polymorphism. ¬†From the following examples, state which ones would be most efficiently implemented through inheritance:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
(A) There are two main kinds of sandwiches that have many properties in common: a vegetarian sandwich and a sandwich with meat&lt;br /&gt;
&lt;br /&gt;
(B) A¬†grocery cart contains lots of different items&lt;br /&gt;
&lt;br /&gt;
(C)¬†A megazord has a lot of smaller zoid's&lt;br /&gt;
&lt;br /&gt;
(D) Lots of people apply for the same job&lt;br /&gt;
&lt;br /&gt;
(E)¬†Types of transportation include bikes, cars, and kodo's&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A - 5&lt;br /&gt;
&lt;br /&gt;
Answer: ¬†A, E&lt;br /&gt;
&lt;br /&gt;
Q7 - Casting&lt;br /&gt;
&lt;br /&gt;
A superclass, SuperSaiyan, has a subclass SuperSaiyan2, which has a subclass SuperSaiyan3.¬† These are instantiated as &amp;quot;ss&amp;quot;, &amp;quot;ss2&amp;quot;, and &amp;quot;ss3&amp;quot; respectively.¬† How can the SuperSaiyan2 object be declared as a SuperSaiyan?&lt;br /&gt;
&lt;br /&gt;
Q7 - Answer&lt;br /&gt;
&lt;br /&gt;
ss2 = (SuperSaiyan2) ss;&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Casting is required when moving up the object hierarchy.&lt;br /&gt;
&lt;br /&gt;
Q7S - Overloading/Overriding&lt;br /&gt;
&lt;br /&gt;
Following the same premise:¬† A superclass, SuperSaiyan, has a subclass SuperSaiyan2, which has a subclass SuperSaiyan3.¬† These are instantiated as &amp;quot;ss&amp;quot;, &amp;quot;ss2&amp;quot;, and &amp;quot;ss3&amp;quot; respectively.¬†¬†&lt;br /&gt;
&lt;br /&gt;
¬†&lt;br /&gt;
&lt;br /&gt;
SuperSaiyan has the method void increasePower(int i).¬† SuperSaiyan2 has the method void increasePower(int i, int j).¬† SuperSaiyan3 has the method void increasePower(int i, int j, int k).&lt;br /&gt;
&lt;br /&gt;
¬†&lt;br /&gt;
&lt;br /&gt;
Is this an example of overloading, overriding, both, or neither? &lt;br /&gt;
&lt;br /&gt;
Q7S - Answer&lt;br /&gt;
&lt;br /&gt;
overloading&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Although method names are common, the parameters differ.¬† Subclasses will have access to both their own increasePower method and the superclass increasePower method(s).¬† &lt;br /&gt;
&lt;br /&gt;
A - 7&lt;br /&gt;
&lt;br /&gt;
Answer: FREEEZAAAA KILLZZZ ALLLLLL ARRRGGGGG&lt;br /&gt;
&lt;br /&gt;
¬†&lt;br /&gt;
&lt;br /&gt;
But the scouter says over 9000! haha i wish i could remember wut that meant :(&lt;br /&gt;
&lt;br /&gt;
Q7- Overloading&lt;br /&gt;
&lt;br /&gt;
Does the following code implement overloading? If so, how? If not, what is wrong with the code?&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
public int deposit(int accountNumber, double depositAmount){&lt;br /&gt;
&lt;br /&gt;
¬†¬† ¬†...&lt;br /&gt;
&lt;br /&gt;
}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
public double deposit(int accountNumber, double depositAmount){&lt;br /&gt;
&lt;br /&gt;
¬†¬† ¬†...&lt;br /&gt;
&lt;br /&gt;
}&lt;br /&gt;
&lt;br /&gt;
Q7 Answer&lt;br /&gt;
&lt;br /&gt;
No, the code doesn't utilize overloading because even though the return types are different, the parameters are the same. ¬†&lt;br /&gt;
&lt;br /&gt;
Q8- Casting&lt;br /&gt;
&lt;br /&gt;
fill in the blank to contruct an instance of Internet :&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
public class Wireless extends Internet{&lt;br /&gt;
&lt;br /&gt;
¬†¬† ¬†Wireless wifi;&lt;br /&gt;
&lt;br /&gt;
¬†¬† ¬†Internet router1 = ¬†_______ wifi;&lt;br /&gt;
&lt;br /&gt;
Q8- Answer&lt;br /&gt;
&lt;br /&gt;
Internet router1 = ¬†(Internet) wifi;&lt;br /&gt;
&lt;br /&gt;
Q9&lt;br /&gt;
&lt;br /&gt;
fix the error relating specifically to overloading:&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
public interface Drivable{&lt;br /&gt;
&lt;br /&gt;
¬†¬† ¬†public double accelerate(){&lt;br /&gt;
&lt;br /&gt;
¬†¬† ¬†.....¬†&lt;br /&gt;
&lt;br /&gt;
¬†¬† ¬†return newSpeed;&lt;br /&gt;
&lt;br /&gt;
¬†¬† ¬†}&lt;br /&gt;
&lt;br /&gt;
}&lt;br /&gt;
&lt;br /&gt;
public class Bike extends Drivable{&lt;br /&gt;
&lt;br /&gt;
¬†¬† ¬†Bike tricycle;&lt;br /&gt;
&lt;br /&gt;
¬†¬† ¬†double newSpeed;&lt;br /&gt;
&lt;br /&gt;
¬†¬† ¬†newSpeed =¬†tricycle.accelerate(double speedChange);¬†&lt;br /&gt;
&lt;br /&gt;
}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
showdown question: fix the other error (the answer is not related to constructors&lt;br /&gt;
&lt;br /&gt;
Q9 Answer&lt;br /&gt;
&lt;br /&gt;
Answer: turn the accelerate method in Drivable to:&lt;br /&gt;
&lt;br /&gt;
¬†¬† ¬†public double accelerate(double speedChange){&lt;br /&gt;
&lt;br /&gt;
¬†¬† ¬†...&lt;br /&gt;
&lt;br /&gt;
¬†¬† ¬†return newSpeed;&lt;br /&gt;
&lt;br /&gt;
¬†¬† ¬†}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Showdown Answer: create a method in the Bike class into which the method call tricycle.accelerate(...) can be written&lt;br /&gt;
&lt;br /&gt;
Q10&lt;br /&gt;
&lt;br /&gt;
¬†&lt;br /&gt;
&lt;br /&gt;
¬†&lt;br /&gt;
&lt;br /&gt;
What must be true if a child of an abstract parent class does not override all of the parent's abstract methods?&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
a.¬†¬†¬† This is always an error.&lt;br /&gt;
b.¬†¬†¬† The child class itself must be declared to be abstract.&lt;br /&gt;
c.¬†¬†¬† Child classes are automatically non-abstract, so this is OK.&lt;br /&gt;
d.¬†¬†¬† The parent class is in error. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A9&lt;br /&gt;
&lt;br /&gt;
B&lt;br /&gt;
&lt;br /&gt;
Q10S&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
What must a non-abstract child do about an abstract method in its parent class?&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
a.¬†¬†¬† A child must override an abstract method inherited from its parent by defining a method with the same signature and same return type.&lt;br /&gt;
b.¬†¬†¬† A child must define an additional method similar to the one inherited from its parent by defining a method with the same signature and different return type.&lt;br /&gt;
c.¬†¬†¬† A child must not define any method with the same signature as the parent's abstract method.&lt;br /&gt;
d.¬†¬†¬† A non-abstract child must define an abstract method with the same signature and same return type as the parent's abstract method.¬† &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
A10S&lt;br /&gt;
&lt;br /&gt;
A&lt;br /&gt;
&lt;br /&gt;
Q11&lt;br /&gt;
&lt;br /&gt;
What is the apparent type of an object? ¬† &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
¬† A. The type of the expression that uses the object (your answer)&lt;br /&gt;
&lt;br /&gt;
B. The result of the toString() method ¬† ¬†&lt;br /&gt;
&lt;br /&gt;
C. the subtype of the object ¬†&lt;br /&gt;
&lt;br /&gt;
D. the class used to instantiate the object &lt;br /&gt;
&lt;br /&gt;
Q11A&lt;br /&gt;
&lt;br /&gt;
A&lt;br /&gt;
&lt;br /&gt;
Q11S&lt;br /&gt;
&lt;br /&gt;
An apparent type is always what?&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
¬† A. a subtype of the actual type ¬† ¬†&lt;br /&gt;
&lt;br /&gt;
B. the same for each instance (your answer) ¬†¬†&lt;br /&gt;
&lt;br /&gt;
C. a supertype of the actual type (correct answer) ¬†&lt;br /&gt;
&lt;br /&gt;
¬† D. None of the above &lt;br /&gt;
&lt;br /&gt;
Q11SA&lt;br /&gt;
&lt;br /&gt;
C&lt;br /&gt;
&lt;br /&gt;
Q12&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
¬†&lt;br /&gt;
&lt;br /&gt;
¬†&lt;br /&gt;
&lt;br /&gt;
¬†&lt;br /&gt;
&lt;br /&gt;
Say that class Rodent has a child class Rat and another child class Mouse. Class Mouse has a child class MiniMouse. Examine the following&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
¬†¬†¬† Rodent rod;&lt;br /&gt;
¬†¬†¬† Rat rat = new Rat();&lt;br /&gt;
¬†¬†¬† Mouse mos = new Mouse();&lt;br /&gt;
¬†¬†¬† MiniMouse min = new Minimouse();&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Which one of the following will cause a compiler error?&lt;br /&gt;
a.¬†¬†¬† rod = rat; b.¬†¬†¬† rod = mos; c.¬†¬†¬† min = null; d.¬†¬†¬† min = rat; &lt;br /&gt;
&lt;br /&gt;
Q12A&lt;br /&gt;
&lt;br /&gt;
D&lt;br /&gt;
&lt;br /&gt;
Q12S&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Say that the situation is the same as in the previous question. Which of the following array declarations is correct for an array that is expected to hold up to 10 objects of types Rat, Mouse, and MiniMouse?&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
a.¬†¬†¬† Rat[] array = new Rat[10];&lt;br /&gt;
b.¬†¬†¬† Rodent[] array = new Rat[10];&lt;br /&gt;
c.¬†¬†¬† Rodent[] array = new Rodent[10];&lt;br /&gt;
d.¬†¬†¬† Rodent[10] array; &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Q12SA&lt;br /&gt;
&lt;br /&gt;
C&lt;br /&gt;
&lt;br /&gt;
Q13&lt;br /&gt;
&lt;br /&gt;
What must a non-abstract child do about an abstract method in its parent class?&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
a.¬†¬†¬† A child must override an abstract method inherited from its parent by defining a method with the same signature and same return type.&lt;br /&gt;
b.¬†¬†¬† A child must define an additional method similar to the one inherited from its parent by defining a method with the same signature and different return type.&lt;br /&gt;
c.¬†¬†¬† A child must not define any method with the same signature as the parent's abstract method.&lt;br /&gt;
d.¬†¬†¬† A non-abstract child must define an abstract method with the same signature and same return type as the parent's abstract method. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Q13A&lt;br /&gt;
&lt;br /&gt;
A&lt;br /&gt;
&lt;br /&gt;
Q13S&lt;br /&gt;
&lt;br /&gt;
¬†&lt;br /&gt;
&lt;br /&gt;
¬†&lt;br /&gt;
&lt;br /&gt;
What must be true if a child of an abstract parent class does not override all of the parent's abstract methods?&lt;br /&gt;
¬†&lt;br /&gt;
&lt;br /&gt;
¬†&lt;br /&gt;
&lt;br /&gt;
a.¬†¬†¬† This is always an error.&lt;br /&gt;
b.¬†¬†¬† The child class itself must be declared to be abstract.&lt;br /&gt;
c.¬†¬†¬† Child classes are automatically non-abstract, so this is OK.&lt;br /&gt;
d.¬†¬†¬† The parent class is in error. &lt;br /&gt;
&lt;br /&gt;
Q13SA&lt;br /&gt;
&lt;br /&gt;
B&lt;br /&gt;
&lt;br /&gt;
Q14&lt;br /&gt;
&lt;br /&gt;
Fill in the blanks: &lt;br /&gt;
&lt;br /&gt;
¬†&lt;br /&gt;
&lt;br /&gt;
¬†&lt;br /&gt;
&lt;br /&gt;
public interface Cat&lt;br /&gt;
{&lt;br /&gt;
¬†¬†¬† public void print();&lt;br /&gt;
}&lt;br /&gt;
¬†&lt;br /&gt;
class Dog ______ Cat&lt;br /&gt;
{&lt;br /&gt;
¬†¬† public void print() { System.out.println(&amp;quot;I&amp;quot;m a Cat and a ____&amp;quot;); }&lt;br /&gt;
}&lt;br /&gt;
¬†&lt;br /&gt;
class Zebra ______ Cat&lt;br /&gt;
{&lt;br /&gt;
¬†¬† public void print() { System.out.println(&amp;quot;I'm a ___ and a ____&amp;quot;); }&lt;br /&gt;
}&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Q14A&lt;br /&gt;
&lt;br /&gt;
implements&lt;br /&gt;
Dog&lt;br /&gt;
implements&lt;br /&gt;
Cat&lt;br /&gt;
Zebra&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Q14S&lt;br /&gt;
&lt;br /&gt;
Was the previous example a case of Overriding or Overloading?&lt;br /&gt;
&lt;br /&gt;
Q14SA&lt;br /&gt;
&lt;br /&gt;
Overriding&lt;br /&gt;
&lt;br /&gt;
True or false?&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
When overloading...&lt;br /&gt;
&lt;br /&gt;
¬†&lt;br /&gt;
&lt;br /&gt;
¬†&lt;br /&gt;
&lt;br /&gt;
The return types MUST be the same.&lt;br /&gt;
&lt;br /&gt;
For a valid overload you must change more than the return type.&lt;br /&gt;
&lt;br /&gt;
It is not possible to vary the access levels in any direction.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
Q15&lt;br /&gt;
&lt;br /&gt;
Q15A&lt;br /&gt;
&lt;br /&gt;
F&lt;br /&gt;
T&lt;br /&gt;
F&lt;br /&gt;
&lt;br /&gt;
Q15S&lt;br /&gt;
&lt;br /&gt;
True or false?&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
When overriding...&lt;br /&gt;
&lt;br /&gt;
¬†&lt;br /&gt;
&lt;br /&gt;
¬†&lt;br /&gt;
&lt;br /&gt;
Arguments can be different as long as return types are not compatible.&lt;br /&gt;
&lt;br /&gt;
The access level may be different and the method can be less accessible.&lt;br /&gt;
&lt;br /&gt;
Arguments and return types of the overriding method must be seen exactly like the overridden method in the super class.&lt;br /&gt;
&lt;br /&gt;
Q15SA&lt;br /&gt;
&lt;br /&gt;
F&lt;br /&gt;
&lt;br /&gt;
F&lt;br /&gt;
&lt;br /&gt;
T&lt;/div&gt;</summary>
		<author><name>Dcdulin</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC_216_F09/polymorphism_showdown&amp;diff=27970</id>
		<title>CSC 216 F09/polymorphism showdown</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC_216_F09/polymorphism_showdown&amp;diff=27970"/>
		<updated>2009-11-18T03:48:16Z</updated>

		<summary type="html">&lt;p&gt;Dcdulin: /* Participants and Props */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Jim Creager and Davis Dulin'''&lt;br /&gt;
&lt;br /&gt;
==Polymorphism - Changing the Shape of Your Program==&lt;br /&gt;
&lt;br /&gt;
Polymorphism is the ability of a subclass to define new or share functionality with a superclass.  A subclass automatically has possession of public and protected variables and methods in its superclass.  These inherited variables and methods can be called directly from an object of the subclass without having to change type.  &lt;br /&gt;
&lt;br /&gt;
===Overriding===&lt;br /&gt;
It is also possible to redefine variables and methods within a subclass.  In such a case, a variable/method defined in the subclass '''overrides''' the variable/method with the same name in the superclass.  When called from an instance of the subclass, the variable/method defined in the subclass will be accessed instead of the one in the superclass.&lt;br /&gt;
&lt;br /&gt;
===Overloading===&lt;br /&gt;
'''Overloading''' is a technique by which a method takes on many forms.  Overloading occurs when a method name is used multiple times, but each instance of the method contains different parameters.  This allows multiple variations of the same action to occur depending on circumstances.&lt;br /&gt;
&lt;br /&gt;
===Casting===&lt;br /&gt;
Polymorphism also allows objects of one class to be transformed into objects of another class.  This is particularly useful when changing functionality in an inheritance relationship.  An instance of the superclass’ type can be set equal to an instance of the subclass’ type without any conflicts in the program.  This is because the subclass is a more specific class of the superclass.  Moving from subclass to superclass, however, would be making the subclass more generic.  A technique known as casting is required to perform this change.  '''Casting''' objects is only valid when moving in a upward along an object’s hierarchy (up to the superclass).  Casting cannot be used between objects on the same level of the object hierarchy, and casting is not necessary to move down the object hierarchy.  By placing a superclass’ name in parentheses just before the object you want to transform, you are declaring a new type, or casting.&lt;br /&gt;
&lt;br /&gt;
==Polymorphism Showdown - The Game==&lt;br /&gt;
&lt;br /&gt;
Polymorphism Showdown is a quiz-based game that tests knowledge of polymorphism concepts with relation to inheritance.  The goal is to familiarize participants with casting, overloading, and overriding.  Questions use a variety of formats, including UML diagrams and code snippets, to acclimate participants to conceptual application and direct code application.  Participants are required to think on their feet and answer quickly so that an active audience is maintained and learning continues.&lt;br /&gt;
&lt;br /&gt;
===Participants and Props===&lt;br /&gt;
Required:  [[PowerPoint]] slideshow of quiz questions, [http://spreadsheets.google.com/viewform?formkey=dHRISWdoc290c0hPOEJRVG1NSXlvYVE6MA GoogleDocs answer form], [http://spreadsheets.google.com/ccc?key=ttHIghsotsHO8BQTmMIyoaQ corresponding GoogleDocs spreadsheet], and a chalkboard/whiteboard for score keeping.&lt;br /&gt;
&lt;br /&gt;
The entire class participates in this exercise.  Students attempt quiz problems as individuals while earning points for their team.  Rows compete against each other to earn the highest score.&lt;br /&gt;
&lt;br /&gt;
===How It Works===&lt;br /&gt;
There will be two types of questions in the game:  free-for-all and showdown.  Numbered questions indicate a free-for-all type in which all students participate.  Numbered questions followed by an ‘S’ indicate a showdown type in which select students participate.  All students attempt to correctly answer free-for-all problems as fast as possible.  The first student from each row to answer correctly advances to the showdown round as a representative for his/her row.  The first student to correctly answer the showdown problem receives a point for his/her row.  &lt;br /&gt;
&lt;br /&gt;
===Steps===&lt;br /&gt;
# The instructor should first create tally columns on the chalkboard/whiteboard for each row of students in the classroom.&lt;br /&gt;
# The instructor should then bring up the Polymorphism Showdown PowerPoint on the display.  The option is given on the home slide to review polymorphism concepts, review game instructions, or skip straight to the questions.&lt;br /&gt;
# When ready to begin the game, a link to the GoogleDoc answer form will need to be provided to the students.  At this time, the instructor should pull up the form’s corresponding spreadsheet on another computer or a second window.&lt;br /&gt;
# To begin the exercise, every student should fill in the next question number, his/her initials, and his/her row number on the GoogleDoc answer form.  The answer text field should be left blank, and the form should NOT yet be submitted.&lt;br /&gt;
# The instructor should then count down and flip the PowerPoint to the slide containing the next question.&lt;br /&gt;
# Students are to answer and submit the form as fast as possible.  Each student should only submit once.&lt;br /&gt;
# After 30 seconds, the instructor should prevent the spreadsheet from accepting submissions.  The PowerPoint can then be changed to the next slide which contains the answer.&lt;br /&gt;
# The instructor should then sort data in the spreadsheet by right clicking the “Row Number” column and selecting “From A-Z.”  This will organize answers into groups of row 1, row 2, etc., and answers within each group will be in order of time submitted (earliest first).&lt;br /&gt;
# The first person from each row to submit the correct answer (identified by initials) is then designated to participate in the next question, a showdown between rows.&lt;br /&gt;
# After designating the representatives for each row, the instructor should clear the data cells of the spreadsheet.  Submissions should be permitted once again.  This allows the same form and spreadsheet to be reused.&lt;br /&gt;
# Row representatives then revisit the GoogleDoc form and fill out entries as before, this time selecting the appropriate showdown question number.&lt;br /&gt;
# The instructor counts down and the PowerPoint is flipped to the next slide which contains the showdown question.&lt;br /&gt;
# Students are to answer and submit as fast as possible.&lt;br /&gt;
# Data will fill the spreadsheet in order of time submitted.  When the first correct answer arrives, the instructor should announce that there is a winner and stop further submissions from being received.&lt;br /&gt;
# The instructor then adds a tally to the chalkboard/whiteboard for the row that the winner represents.&lt;br /&gt;
# The instructor should clear the data cells of the spreadsheet.  Submissions should be permitted once again.  &lt;br /&gt;
# Steps 4-16 are repeated for remaining questions.&lt;/div&gt;</summary>
		<author><name>Dcdulin</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC_216_F09/polymorphism_showdown&amp;diff=27473</id>
		<title>CSC 216 F09/polymorphism showdown</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC_216_F09/polymorphism_showdown&amp;diff=27473"/>
		<updated>2009-11-17T18:41:28Z</updated>

		<summary type="html">&lt;p&gt;Dcdulin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;'''Jim Creager and Davis Dulin'''&lt;br /&gt;
&lt;br /&gt;
===Formatting Resources===&lt;br /&gt;
[http://meta.wikimedia.org/wiki/Help:Wikitext_examples Formatting Help Guide from MetaWiki]&lt;br /&gt;
&lt;br /&gt;
==Polymorphism - Changing the Shape of Your Program==&lt;br /&gt;
&lt;br /&gt;
Polymorphism is the ability of a subclass to define new or share functionality with a superclass.  A subclass automatically has possession of public and protected variables and methods in its superclass.  These inherited variables and methods can be called directly from an object of the subclass without having to change type.  It is possible to redefine variables and methods within a subclass.  This creates functionality.  In such a case, a variable or method with the same name defined in the subclass overrides the functionality with the same name of the superclass. &lt;br /&gt;
overload many forms&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
===The problem===&lt;br /&gt;
&lt;br /&gt;
Describe what you are attempting to teach students by this exercise.&lt;br /&gt;
&lt;br /&gt;
===Participants and props===&lt;br /&gt;
&lt;br /&gt;
How many students will participate?  What else do you need (e.g., old tennis ball, Powerpoint slides, software).&lt;br /&gt;
&lt;br /&gt;
===The script===&lt;br /&gt;
&lt;br /&gt;
Describe how to do your exercise.&lt;/div&gt;</summary>
		<author><name>Dcdulin</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC_216_F09/polymorphism_showdown&amp;diff=27472</id>
		<title>CSC 216 F09/polymorphism showdown</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC_216_F09/polymorphism_showdown&amp;diff=27472"/>
		<updated>2009-11-17T18:40:29Z</updated>

		<summary type="html">&lt;p&gt;Dcdulin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;#REDIRECT [[polymorphism]]&lt;/div&gt;</summary>
		<author><name>Dcdulin</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC_216_F09/polymorphism_showdown&amp;diff=27471</id>
		<title>CSC 216 F09/polymorphism showdown</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC_216_F09/polymorphism_showdown&amp;diff=27471"/>
		<updated>2009-11-17T18:40:20Z</updated>

		<summary type="html">&lt;p&gt;Dcdulin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;#REDIRECT [[polymorphism Polymorphism Showdown]]&lt;/div&gt;</summary>
		<author><name>Dcdulin</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC_216_F09/polymorphism_showdown&amp;diff=27470</id>
		<title>CSC 216 F09/polymorphism showdown</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC_216_F09/polymorphism_showdown&amp;diff=27470"/>
		<updated>2009-11-17T18:39:57Z</updated>

		<summary type="html">&lt;p&gt;Dcdulin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;#REDIRECT [[Polymorphism Showdown]]&lt;/div&gt;</summary>
		<author><name>Dcdulin</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC_216_F09/polymorphism_showdown&amp;diff=27467</id>
		<title>CSC 216 F09/polymorphism showdown</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC_216_F09/polymorphism_showdown&amp;diff=27467"/>
		<updated>2009-11-17T18:39:14Z</updated>

		<summary type="html">&lt;p&gt;Dcdulin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;#REDIRECT [[http://pg-server.csc.ncsu.edu/mediawiki/index.php/CSC_216_F09/polymorphism Polymorphism Showdown]]&lt;/div&gt;</summary>
		<author><name>Dcdulin</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC_216_F09/polymorphism_showdown&amp;diff=27465</id>
		<title>CSC 216 F09/polymorphism showdown</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC_216_F09/polymorphism_showdown&amp;diff=27465"/>
		<updated>2009-11-17T18:38:57Z</updated>

		<summary type="html">&lt;p&gt;Dcdulin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;REDIRECT# [[http://pg-server.csc.ncsu.edu/mediawiki/index.php/CSC_216_F09/polymorphism Polymorphism Showdown]]&lt;/div&gt;</summary>
		<author><name>Dcdulin</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC_216_F09/_VisualExceptionHandlingExercise&amp;diff=27464</id>
		<title>CSC 216 F09/ VisualExceptionHandlingExercise</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC_216_F09/_VisualExceptionHandlingExercise&amp;diff=27464"/>
		<updated>2009-11-17T18:38:41Z</updated>

		<summary type="html">&lt;p&gt;Dcdulin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Visual Exception Handling Excercise]]&lt;br /&gt;
&lt;br /&gt;
[[http://pg-server.csc.ncsu.edu/mediawiki/index.php/CSC_216_F09/polymorphism_showdown Polymorphism Showdown]]&lt;br /&gt;
&lt;br /&gt;
==Exercises==&lt;br /&gt;
&lt;br /&gt;
===Inheritance===&lt;br /&gt;
&lt;br /&gt;
===GUIs===&lt;br /&gt;
&lt;br /&gt;
===Data Structure Jeopardy===&lt;/div&gt;</summary>
		<author><name>Dcdulin</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC_216_F09/_VisualExceptionHandlingExercise&amp;diff=27462</id>
		<title>CSC 216 F09/ VisualExceptionHandlingExercise</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC_216_F09/_VisualExceptionHandlingExercise&amp;diff=27462"/>
		<updated>2009-11-17T18:37:35Z</updated>

		<summary type="html">&lt;p&gt;Dcdulin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Visual Exception Handling Excercise]]&lt;br /&gt;
&lt;br /&gt;
[[http://pg-server.csc.ncsu.edu/mediawiki/index.php/CSC_216_F09/polymorphism Polymorphism Showdown]]&lt;br /&gt;
&lt;br /&gt;
==Exercises==&lt;br /&gt;
&lt;br /&gt;
===Inheritance===&lt;br /&gt;
&lt;br /&gt;
===GUIs===&lt;br /&gt;
&lt;br /&gt;
===Data Structure Jeopardy===&lt;/div&gt;</summary>
		<author><name>Dcdulin</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC_216_F09/_VisualExceptionHandlingExercise&amp;diff=27454</id>
		<title>CSC 216 F09/ VisualExceptionHandlingExercise</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC_216_F09/_VisualExceptionHandlingExercise&amp;diff=27454"/>
		<updated>2009-11-17T18:35:50Z</updated>

		<summary type="html">&lt;p&gt;Dcdulin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Visual Exception Handling Excercise]]&lt;br /&gt;
&lt;br /&gt;
[[http://pg-server.csc.ncsu.edu/mediawiki/index.php/CSC_216_F09/polymorphism_showdown Polymorphism Showdown]]&lt;br /&gt;
&lt;br /&gt;
==Exercises==&lt;br /&gt;
&lt;br /&gt;
===Inheritance===&lt;br /&gt;
&lt;br /&gt;
===GUIs===&lt;/div&gt;</summary>
		<author><name>Dcdulin</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC_216_F09/_VisualExceptionHandlingExercise&amp;diff=27452</id>
		<title>CSC 216 F09/ VisualExceptionHandlingExercise</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC_216_F09/_VisualExceptionHandlingExercise&amp;diff=27452"/>
		<updated>2009-11-17T18:35:30Z</updated>

		<summary type="html">&lt;p&gt;Dcdulin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Visual Exception Handling Excercise]]&lt;br /&gt;
&lt;br /&gt;
[[http://pg-server.csc.ncsu.edu/mediawiki/index.php/CSC_216_F09/polymorphism Polymorphism Showdown]]&lt;br /&gt;
&lt;br /&gt;
==Exercises==&lt;br /&gt;
&lt;br /&gt;
===Inheritance===&lt;br /&gt;
&lt;br /&gt;
===GUIs===&lt;/div&gt;</summary>
		<author><name>Dcdulin</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC_216_F09/_VisualExceptionHandlingExercise&amp;diff=27450</id>
		<title>CSC 216 F09/ VisualExceptionHandlingExercise</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC_216_F09/_VisualExceptionHandlingExercise&amp;diff=27450"/>
		<updated>2009-11-17T18:35:17Z</updated>

		<summary type="html">&lt;p&gt;Dcdulin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Visual Exception Handling Excercise]]&lt;br /&gt;
&lt;br /&gt;
[[http://pg-server.csc.ncsu.edu/mediawiki/index.php/CSC_216_F09/polymorphism_showdown Polymorphism Showdown]]&lt;br /&gt;
&lt;br /&gt;
==Exercises==&lt;br /&gt;
&lt;br /&gt;
===Inheritance===&lt;br /&gt;
&lt;br /&gt;
===GUIs===&lt;/div&gt;</summary>
		<author><name>Dcdulin</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC_216_F09/_VisualExceptionHandlingExercise&amp;diff=27448</id>
		<title>CSC 216 F09/ VisualExceptionHandlingExercise</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC_216_F09/_VisualExceptionHandlingExercise&amp;diff=27448"/>
		<updated>2009-11-17T18:34:18Z</updated>

		<summary type="html">&lt;p&gt;Dcdulin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Visual Exception Handling Excercise]]&lt;br /&gt;
&lt;br /&gt;
[[http://pg-server.csc.ncsu.edu/mediawiki/index.php/CSC_216_F09/polymorphism Polymorphism Showdown]]&lt;br /&gt;
&lt;br /&gt;
==Exercises==&lt;br /&gt;
&lt;br /&gt;
===Inheritance===&lt;br /&gt;
&lt;br /&gt;
===GUIs===&lt;/div&gt;</summary>
		<author><name>Dcdulin</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC_216_F09/_VisualExceptionHandlingExercise&amp;diff=27426</id>
		<title>CSC 216 F09/ VisualExceptionHandlingExercise</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC_216_F09/_VisualExceptionHandlingExercise&amp;diff=27426"/>
		<updated>2009-11-17T18:28:48Z</updated>

		<summary type="html">&lt;p&gt;Dcdulin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Visual Exception Handling Excercise]]&lt;br /&gt;
&lt;br /&gt;
[[http://pg-server.csc.ncsu.edu/mediawiki/index.php/CSC_216_F09/polymorphism Polymorphism]]&lt;br /&gt;
&lt;br /&gt;
==Exercises==&lt;br /&gt;
&lt;br /&gt;
===Inheritance===&lt;br /&gt;
&lt;br /&gt;
===GUIs===&lt;/div&gt;</summary>
		<author><name>Dcdulin</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC_216_F09/_VisualExceptionHandlingExercise&amp;diff=27424</id>
		<title>CSC 216 F09/ VisualExceptionHandlingExercise</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC_216_F09/_VisualExceptionHandlingExercise&amp;diff=27424"/>
		<updated>2009-11-17T18:28:37Z</updated>

		<summary type="html">&lt;p&gt;Dcdulin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Visual Exception Handling Excercise]]&lt;br /&gt;
&lt;br /&gt;
[[polymorphism]]&lt;br /&gt;
&lt;br /&gt;
==Exercises==&lt;br /&gt;
&lt;br /&gt;
===Inheritance===&lt;br /&gt;
&lt;br /&gt;
===GUIs===&lt;/div&gt;</summary>
		<author><name>Dcdulin</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC_216_F09/_VisualExceptionHandlingExercise&amp;diff=27421</id>
		<title>CSC 216 F09/ VisualExceptionHandlingExercise</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC_216_F09/_VisualExceptionHandlingExercise&amp;diff=27421"/>
		<updated>2009-11-17T18:28:04Z</updated>

		<summary type="html">&lt;p&gt;Dcdulin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Visual Exception Handling Excercise]]&lt;br /&gt;
&lt;br /&gt;
[[http://pg-server.csc.ncsu.edu/mediawiki/index.php/CSC_216_F09/polymorphism Polymorphism]]&lt;br /&gt;
&lt;br /&gt;
==Exercises==&lt;br /&gt;
&lt;br /&gt;
===Inheritance===&lt;br /&gt;
&lt;br /&gt;
===GUIs===&lt;/div&gt;</summary>
		<author><name>Dcdulin</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC_216_F09/_VisualExceptionHandlingExercise&amp;diff=27416</id>
		<title>CSC 216 F09/ VisualExceptionHandlingExercise</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC_216_F09/_VisualExceptionHandlingExercise&amp;diff=27416"/>
		<updated>2009-11-17T18:26:26Z</updated>

		<summary type="html">&lt;p&gt;Dcdulin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;#REDIRECT [[Visual Exception Handling Excercise]]&lt;br /&gt;
[[http://pg-server.csc.ncsu.edu/mediawiki/index.php/CSC_216_F09/polymorphism Polymorphism]]&lt;br /&gt;
&lt;br /&gt;
==Exercises==&lt;br /&gt;
&lt;br /&gt;
===Inheritance===&lt;br /&gt;
&lt;br /&gt;
===GUIs===&lt;/div&gt;</summary>
		<author><name>Dcdulin</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC_216_F09/_VisualExceptionHandlingExercise&amp;diff=27412</id>
		<title>CSC 216 F09/ VisualExceptionHandlingExercise</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC_216_F09/_VisualExceptionHandlingExercise&amp;diff=27412"/>
		<updated>2009-11-17T18:24:51Z</updated>

		<summary type="html">&lt;p&gt;Dcdulin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;#REDIRECT [[Visual Exception Handling Excercise]]&lt;br /&gt;
&lt;br /&gt;
==Exercises==&lt;br /&gt;
&lt;br /&gt;
===Inheritance===&lt;br /&gt;
&lt;br /&gt;
===GUIs===&lt;br /&gt;
&lt;br /&gt;
#REDIRECT [[http://pg-server.csc.ncsu.edu/mediawiki/index.php/CSC_216_F09/polymorphism Polymorphism]]&lt;/div&gt;</summary>
		<author><name>Dcdulin</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC_216_F09/_VisualExceptionHandlingExercise&amp;diff=27408</id>
		<title>CSC 216 F09/ VisualExceptionHandlingExercise</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC_216_F09/_VisualExceptionHandlingExercise&amp;diff=27408"/>
		<updated>2009-11-17T18:24:05Z</updated>

		<summary type="html">&lt;p&gt;Dcdulin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;#REDIRECT [[Visual Exception Handling Excercise]]&lt;br /&gt;
&lt;br /&gt;
==Exercises==&lt;br /&gt;
&lt;br /&gt;
===Inheritance===&lt;br /&gt;
&lt;br /&gt;
===GUIs===&lt;br /&gt;
&lt;br /&gt;
[[polymorphism]]&lt;/div&gt;</summary>
		<author><name>Dcdulin</name></author>
	</entry>
	<entry>
		<id>https://wiki.expertiza.ncsu.edu/index.php?title=CSC_216_F09/_VisualExceptionHandlingExercise&amp;diff=27405</id>
		<title>CSC 216 F09/ VisualExceptionHandlingExercise</title>
		<link rel="alternate" type="text/html" href="https://wiki.expertiza.ncsu.edu/index.php?title=CSC_216_F09/_VisualExceptionHandlingExercise&amp;diff=27405"/>
		<updated>2009-11-17T18:23:32Z</updated>

		<summary type="html">&lt;p&gt;Dcdulin: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;#REDIRECT [[Visual Exception Handling Excercise]]&lt;br /&gt;
&lt;br /&gt;
==Exercises==&lt;br /&gt;
&lt;br /&gt;
===Inheritance===&lt;br /&gt;
&lt;br /&gt;
===GUIs===&lt;br /&gt;
&lt;br /&gt;
#REDIRECT [[polymorphism]]&lt;/div&gt;</summary>
		<author><name>Dcdulin</name></author>
	</entry>
</feed>