RE: [PHP] What's the use in OOP?

On Mon, 2004-03-29 at 18:23, Chris Shiflett wrote: > --- Kelly Hallman <khallman@ultrafancy.com> wrote: > > I think there is a bit of what I consider an efficiency myth in > > regards to OOP in PHP. Most agree that the OO implementation in PHP > > is not robust. > > It's much better in PHP 5, although a lack of robustness is not how I > would personally describe PHP 4's shortcomings. > > > However, most people that rely on this assertion do not usually > > understand leveraging OO and also most do not write excellent non-OO > > code. :) > > Perhaps, but I would say that most people who make this assertion > understand OO. The performance penalty is not a myth. Just as templating > incurs a performance penalty, so does OO. The reward can be worth it, of > course, in terms of organization and ease of use. I'd just like to point out as I often do, that the templating system's implementation determines if there is a performance penalty :) compiled-to-source templating systems don't incur such a run-time performance hit, and can in fact increase performance due to the fact the inclusion happens once at the compile stage. This would be akin to inlined code :) Cheers, Rob. -- .------------------------------------------------------------. | InterJinn Application Framework - http://www.interjinn.com | :------------------------------------------------------------: | An application and templating framework for PHP. Boasting | | a powerful, scalable system for accessing system services | | such as forms, properties, sessions, and caches. InterJinn | | also provides an extremely flexible architecture for | | creating re-usable components quickly and easily. | `------------------------------------------------------------'