An important facet of parent-child inheritance is the child's ability to tailor any function that would otherwise be conveyed from the parent. The child-class functions didn't do anything other than slice and forward. They couldn't do much more than that because the child classes inherited all of their data from the parent. Closely related to member function tailoring is the child's ability to go beyond inheritance by adding private member variables, public member variables, and member functions. Adding new m-files is straightforward. Adding new public member variables is a little more difficult because additional variable names need to be incorporated in the group-of-eight functions. Supporting these additions is exactly the reason behind the organization of get.m and set.m. These functions contained slice-and-forward sections only. There was no reason to include sections for public or concealed variables because cStar and cDiamond had none. The paper adds a public variable to cStar and examine the effects on both the implementation and inheritance.

Chapter Contents:

• 14.1 Function Redefinition
• 14.1.1 l@cStar/private/ctor_ini.m with Private Member Variables
• 14.1.2 /@cStar/fieldnames.m with Additional Public Members
• 14.1.3 /@cStar/get.m with Additional Public Members
• 14.1.4 /@cStar/set.m with Additional Public Members
• 14.1.5 /@cStar/draw.m with a Title
• 14.2 Test Drive
• 14.3 Summary
• 14.4 Independent Investigations

Inspec keywords: object-oriented programming

Other keywords: get.m function; cDiamond function; set.m function; m-file; group-of-eight function; Matlab; member function; public member variable; private member variable; cStar function; parent-child function inheritance; child-class function

Subjects: Object-oriented programming