On Sun, 2004-11-14 at 09:30, -{ Rene Brehmer }- wrote:
> Just remember that PHP isn't a true OOP language, so going OOP may not
Please define "true OOP" language and provide a few examples that meet
your criteria. Then show how other examples like PHP fail to meet your
true OOP criteria. Don't forget, if a language has OOP as a subset, it
still has true OOP capabilities. Also it might help to clarify if you
mean PHP in general or PHP4 and below.
> necessarily be the best solution always. OOP makes certain types of
> projects easier to code, and some projects would be almost impossible to do
> without OOP (like anything you wanna do where you need to use scope to
> avoid major headaches), but because PHP isn't compiled or a true OOP
PHP is runtime compiled to bytecode. It's just as compiled as any other
language. With a good compiler cache it's just as compiled as java.
> language, OOP in PHP hampers performance, and that hampering is exponential
> with the complexity of the objects.
You're shitting us all right? Exponential? Really? could you show us
some benchmarks on how it's exponential?
Let's not be sowing seeds of FUD on the PHP general list.
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. |
`------------------------------------------------------------'
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
