RE: [PHP-DEV] parent_ctor()

At 17:46 17-07-00, =?US-ASCII?Q?David_Hjortso?= wrote:

Yes, who knows, and that's the problem. I for one will most likely have to start the project that I'd loved to do in PHP, in java simply because it supports more OO features, and has a better OO implementation (at least feature wise) than PHP. And that IMHO is sad, esp. considering all the good things that PHP has.

Read that paragraph again, it simply makes no sense. If you're forced to do it in Java because you don't like the OO implementation of PHP or it's not powerful enough for you, then it's *NOT* sad at all that you'd use Java. You can't say "I want to do it in PHP, but PHP can't do it at all and its entire implementation and concept doesn't work this way, so I'll do it in Java". If you want the Java OO model and approach you want to do it in Java, period. Don't change PHP to be what it's not and not supposed to be; Use the right tool for the right job. Yes, but code managability and reuse is also a good point when using OO; it

doesnt need to be complicated at all, small apps can be made with OOP just as easily as with non-OOP, but you will find it alot easier to extend and integrate the OO version than the other one. And it's not like bigger projects shouldnt be done in PHP, afterall a simple treestructure, or a shopping solution can be much easier when done in OOP, aswell as complete e-business solutions integrating proprietary economy systems and so on. Saying that just because these are on the web, means that they shouldn't be done in OOP is imho, plain wrong. At least that's what I have found, and I am sure some other people will agree with me.

(Most) Web projects have, and IMO, will always have one major difference from other applications - they are *realtime*, or in other words, they must be fast. I'm not even going to argue about whether OO slows you down or not. I will argue that this does mean that Web project have a firm limit on the amount of growth they can make on the 'vertical' scale (i.e. the amount of complexity layers, as opposed to the 'horizontal' scale, which would be very wide layers, but which are in total, fairly thin). This, in my opinion, makes the cries people make for an advanced, Java-like OO model, quite irrelevant. PHP, as a Web language, isn't likely to benefit from an advanced and less dynamic OO model. I'm not saying that it won't benefit at all - perhaps Kristian would find it indispensable for PHPlib, but the vast majority of Web developers would not. And with all due respect to PHPlib, we won't change the PHP language theme and concept to be a better framework for PHPlib. Zeev -- Zeev Suraski <zeev@zend.com> http://www.zend.com/