Lab46 Wiki

User Tools

Site Tools

You are here: start » notes » cprog » fall2021 » projects » oop2
notes:cprog:fall2021:projects:oop2

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
notes:cprog:fall2021:projects:oop2 [2021/11/11 02:52] – [<fs medium>Similarities to word origins</fs>] zswartwonotes:cprog:fall2021:projects:oop2 [2021/11/11 04:58] (current) – [References] hhemler
Line 133: Line 133:
 Parent child relationships refer to base classes and the derived classes that inherit from them.  In regards to polymorphism, this means, that the derived classes are not simply inheriting attributes or methods, but using them in different ways.  The methods and attributes being inherited still depends on that element's access control label. Parent child relationships refer to base classes and the derived classes that inherit from them.  In regards to polymorphism, this means, that the derived classes are not simply inheriting attributes or methods, but using them in different ways.  The methods and attributes being inherited still depends on that element's access control label.
  
 +Inheritance lets us inherit attributes and methods from another class. Polymorphism uses those methods to perform different tasks.
 ====Similarities to word origins==== ====Similarities to word origins====
 It is strange that what is called 'polymorphism' in C++ is called such. Polymorph's word structure would imply multiple shapes, and polymorph in common fantasy/magical settings often relates to something temporarily transforming into a different creature, or shape. This has no relation to the C++ polymorph, which mainly relates to a child class changing an already existing function of its parent classes. It seems that mutation or evolution would be a better term, as if a creature inherited something from its ancestors, such as eyes, and then the child some genetic variation that caused its eyes to be more effective at seeing, that would be a mutation or evolution, we would not call such a thing polymorphing. It is strange that what is called 'polymorphism' in C++ is called such. Polymorph's word structure would imply multiple shapes, and polymorph in common fantasy/magical settings often relates to something temporarily transforming into a different creature, or shape. This has no relation to the C++ polymorph, which mainly relates to a child class changing an already existing function of its parent classes. It seems that mutation or evolution would be a better term, as if a creature inherited something from its ancestors, such as eyes, and then the child some genetic variation that caused its eyes to be more effective at seeing, that would be a mutation or evolution, we would not call such a thing polymorphing.
Line 154: Line 155:
   * https://www.tutorialspoint.com/cplusplus/cpp_overloading.htm   * https://www.tutorialspoint.com/cplusplus/cpp_overloading.htm
   * https://www.mygreatlearning.com/blog/polymorphism-in-cpp/   * https://www.mygreatlearning.com/blog/polymorphism-in-cpp/
 +  * https://www.javatpoint.com/cpp-virtual-function
 =====Submission===== =====Submission=====
 I'll be looking for the following: I'll be looking for the following:
notes/cprog/fall2021/projects/oop2.1636599136.txt.gz · Last modified: 2021/11/11 02:52 by zswartwo

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
CC Attribution-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki