Hi!
I agree here. Object oriented languages have their place where, and ONLY WHERE, data is the center of focus. When the process is the center of focus, a procedural language makes sense. Trying to make procedures into objects (with a few settings to control their behavior as the 'data' for the class) is nonsense!
afaik (one of) the aims of c++ is that eg. if you have modules in a player, they can inherit the same super-class, and than if you change something in the moduleloading/info structures you only have to change it in one place (the super-class), and than one small change in the api won't give you 1 hour work. Also if eg. a module has a priv struct, that basicly means you are emulating objects in c - to me at least. sure it might not be so efficient in some areas, but an oop language's compiler usually does lot of the work of the human (and is less error prone) if you use the language features wisely. best regards Denes