On Thu, 2003-05-15 at 05:49, D Richard Felker III wrote:
Eg. I prefer object oriented approaches for bigger database driven projects, where code speed doesn't play a primary role. In such case I can have an object keeping track of my database connections and associated data without me needing to keep an eye when to open or close a connection etc.
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!
could you describe this more? i mean for example in the case of mplayer the process is in the center of focus? one could say that mplayer is manipulating with video data, and because of that, mplayer is an application with data in the center of focus. in my experiences, problems can be solved usually as well in procedural as in object oriented way. (of course i'm not talking about very small problems). gabor