>The thing about [OOP] is that it allows you to model a problem domain in real-world terms. >> That's only true on a superficial level. Exactly. I had forgot

>The thing about [OOP] is that it allows you to model a problem domain in real-world terms. >> That's only true on a superficial level. Exactly. I had forgot that I learned OOP by modelling a CD collection. When thinking about it now, "mapping" a program into real-world models and terms seems totally backwards. What's the point of thinking in real-world models unless you program actually manipulates real-world objects? Of course there are properties that are useful to carry over, but why limit your program to real-world models?