Writing
Reflection
“Cout endl!”
By the second week of class, I had heard those same sounds uttered about a hundred times. The sounds had started the first day of “C++ Programming.” Harsh grating sounds, nails on a chalkboard.
There were four of them in a row. They were like drunken soldiers called to attention. All etiquette was thrown aside for the luxury of a dialogue between friends. Undercooked insults flew on puffs of hot air. The scramblers.
“Shhhhsh.”
Like eggs set in their ways, the scramblers didn’t yield to the teacher’s authority. In fact in many ways it just got worse. The longer they were in the pan, the hotter they got.
At that, my shell cracked—they were sucking the white. Like second graders talking during Reading or kindergarteners that wanted to play blocks during naptime. The teacher had to step in.
cout << “The current temperature in Celsius is << celTemp << “.” << endl;
There is no ambiguity here. There can’t be. I won’t allow it. I will spit it back at you saying, “errors: 1, warnings: 0.”
error: line 1, superclass void null;
You can’t cancel an instruction of a superclass. It is unacceptable. The son doesn’t command the Father. The proper hierarchy must be followed to avoid errors. A subclass defining its own inherited attributes creates errors—the logic breaks down and it won’t compile. Code that won’t compile is useless, a waste of space.