A domain class is a class from the Domain Model that Martin Fowler describes as follow in Patterns of Enterprise Application Architecture: An object model of the domain that incorporates both behavior and data. At its worst business logic can be very complex. Rules and logic describe many different cases and slants of behavior, and … Read more
Use base member initialisation: class B : public A { public: B(int a) : A(a) { } ~B(); };
identity: a variable holds the same instance as another variable. equality: two distinct objects can be used interchangeably. they often have the same id. Identity For example: Integer a = new Integer(1); Integer b = a; a is identical to b. In Java, identity is tested with ==. For example, if( a == b ). … Read more
The interesting question here is your question from the comments: What kind of object would you have that you do not need to modify the values at some point? I’m guessing not a model class, correct? I’ve had to change the name of a person in my database – this wouldn’t fit with this idea. … Read more
If you declare a method in a descendant class that has the same name as a method in an ancestor class then you are hiding that ancestor method — meaning if you have an instance of that descendant class (that is referenced as that class) then you will not get the behavior of the ancestor. … Read more
By hiding the variable and adding methods now, the class designer allows for inserting arbitrary code into those methods in the future without breaking tons of code that use the attributes directly. Also note that providing a lot of accessor/mutator methods is generally a sign that your class design needs another look for possible improvement. … Read more
Step one is to adhere to the Single Responsibility Principle. If you can’t say in one sentence what your class does, then it probably does too much. Once you’ve narrowed that down, I don’t know that the number of methods really matters as long as your methods don’t do too much.