@Thorham
OOP uses arrays of function pointers in order to implement inheritable methods. They make those methods have more calling overhead than ordinary functions. It's kind of like the way that the jump tables in shared libraries are slower than a normal function due to the calling overhead.
Yeah, I know, but I don't think function tables are a bad thing... at least not when calling overhead isn't very important.
My major gripe with OO is that it often leads to overdesign by implementing unused methods to make APIs complete, very long inheritance chains etc. OO seems to really get the worst out of (some) mediocre programmers.
And if you look how many times programmers still reinvent the wheel, OO has not fulfilled it's promise of code re-usability either. Don't quote me on it but I think I once read it is inherent with OO and that generic programming is more fit for that.
Yes, but why blame oo for what people do wrong when using oo? It's like blaming your new, sharp knife for getting yourself cut. Would you rather have a blunt knife that doesn't cut well?
Another one is using the right tool for the right job. Using oo for everything is like a carpenter usinmg a hammer for everything. It's just not going to work.
The fact that I got out of programming before it started, so I haven't used it.
:lol:
Then read up on it. It's not very hard to understand and can be very useful sometimes (but not always).
