Have you ever noticed that the more 'OOP' an app is, the slower it is? I tend to try to stay with OOP as much as possible for standardization. However, if it is noticeably faster or easier (and still functions as well) or streamlined the non-oop way instead, then who cares about OOP in that instance...go with what works best. The only time I REALLY try to stay away from something is when it is included ONLY for backwards compatibility. There is too much of a possibility that that function will go away in the future and I'd hate to go through and change all of my code that can no longer be used.


>I've been told that w***() functions (wontop(), wparent(), etc) are not OOP, but I don't understand why.
>
>It seems to me that the arguments that I've heard could be applied to just about any function that existed before OOP.
>ie: "srows()" existed before OOP, so does that make it non-OOP?
>How is that different than "wparent()"?
>
>What am I missing?
>
>TIA