Class Implementation

Encapsulation

A class models a single entity -- one Person, one Car, one Book, one Library.

Classes are used to implement user-defined ADTs. These are classes whose external behavior is known to the class user, but whose internal implemenation is hidden.

But a data type is more than just data..... it also has a set of associated operations. Built-in types like int, float, char have opearations such as add, subtract and multiply. Since the details of these operations are hidden, we can consider the built-in data types to be "Abstract Data Types" (ADTs).

To accomplish this goal, we need a mechanism to hide the details of the class implementation from the class user.

Recall the initial DayOfYear class definition from the text.

Now consider this new improved (but not yet perfect) definition of the DayOfYear class. This definition is adapted from Display 6.4 of the text.

No item that follows the keyword private can be directly referenced by name in any code except the implementations of the class member functions. Attempting to do so results in a compiler error. The compiler enforces the hiding of class details through the use of the keyword private.

Items which follow the keyword public may be referenced in any code, just like members of a struct. Good programming practice, and a REQUIREMENT in this course is that all data members of a class must be declared private.

C++ implements encapsulation by allowing data members to be declared as private. A private datat member will only be accessible to functions that are members of that class and to functions and classes explicitly granted access permission by the class ("friends" -- more on this later).

Member Functions

Member functions that allow the class user to retreive the value of a private data member are known as accessor -- GetDay( ), GetMonthNumber().

Member functions that allow the class user to change the value of a private data member are known as mutators -- both Set( ) functions.

Other member functions generally provide support for the ADTs operations and are often referred to as services -- Input( ), Output( ) As we'll see next time, other special methods are also provided.

Member Function Guidelines

1. Like any well written function, each class' member function should perform just one task and do it well. Private functions may be written and called from the public function to allow proper modularity.
2. No class member function should perform input from or output to the application user unless that is the function's explicit purpose.
   For example, a class that models a Person would likely have an accessor named GetName( ). This function allows the class user access to the data member which contains the Person's name. It DOES NOT prompt the application user to input the Person's name.
3. Although member functions have direct access to private data members, your code should use accessors and mutators whenever available. Doing so further limits the scope of code that needs changed in the future.
4. Proper passing of parameters is vital for efficiency of your program. Pass objects by reference whenever possible (almost always).
5. Also see the guidelines for the use of const.

Example code