Another problem to tackle?

[Valmont]

Just let your functions do as little as possible. Try that first.

[Deliverance]

Do the overloaded operators count as functions, and should I simplify those? I am at a design dilemma here:

1)With my old code, inside my main() function I implicitly read-out the final results by invoking r to the overloaded ostream operator. if I take out the essentials out of that operator, my class will not let me access my data I manipulated without a function. In this case, should I create two more functions (or one) which will display my stats, and if so, doesn't that nullify the existence of my overloaded operators? (i'm using the template red provided)

By the way, I'm still working on this example, I'm just trying to re-read over the chapter on pointers, and string types as I still haven't quite figured out how the last example worked (I understand the logic part but can't trace it onto code, mainly the remove function out of the previous thread that redhead was so kind as to rework for me).

Quick question: I've read that the following type of declaration is legal:

#include <iostream>

void displaythem(int ival, int *pi, int **ppi){std::cout << ival << *pi << **ppi;};
main()
{
   int ival = 1024;
   int *pi = &ival;
   int **ppi = &pi;
   displaythem(ival,pi,ppi); //here we send pi and ppi as to not de-reference them

}

In this simple example, I can perform the operations of pointing to a pointer, and then de-referencing them as to obtain the initial value of ival with all three instances, but when would you need a pointer to a pointer in a programming scenario, which couldn't be achieved (more efficiently) by other means?

[Valmont]

Do the overloaded operators count as functions, and should I simplify those?

Overloaded operators are "conveniance functions". Forget about them until you implemented the class that fullfills the "use case" requirement.

In normal language, first make sure the fundamental behaviour of your class is up and running and AFTER that see how overloaded operators can simplyfie the usage of your class for your client coders (the ones that actually use your class which may include you).