Nowhere did I say that friend classes are bad (or not good) things. I said, in effect, that it is best to grant no more access to data within objects than needed. Friend declarations - be they of friend functions, friend classes, or friend member functions - provide a means for selectively grant access.Originally Posted by std10093
OK...? But window and screen seem tightly coupled anyway. The only reason screen is different from window is because a window can hold several screens. But assuming we're looking for other options... I'm left wondering why there is no Screen::clear() method that window can call.I suppose that we should design our code, like if it was to be handled by 100 programmers, even though it may be just for fun.
Technically, a screen can render several windows too. Goes to show, if you are playing with concepts of windows and screens, you need to be clear about what each of them is and each of them isn't.
In my mind the more autonomous/private something is, the better. It's a matter of precaution. But I think we are about to go off topic..
Code - functions and small libraries I use
It’s 2014 and I still use printf() for debugging.
"Programs must be written for people to read, and only incidentally for machines to execute. " —Harold Abelson
