||*()*|| [\..konnichi wa, ogenki desu ka, Antony../]
>> I might be compenent, but it was a waste of time. I'm not an OOP
>> programmer and I don't like PHP 5 yet.
AD> I could never understand people saying that PHP5 is about OOP.
AD> It's like saying that kernel 2.6 is about desktop.
You will never understand them, because you're core developer, who
knows everything. If you want to know why PHP 5 is about OOP - try
to imagine hosting provider asking "What's new in PHP 5?". Quote
from manual:
"PHP 5 and the integrated Zend Engine 2 have greatly improved PHP's
performance and capabilities, but great care has been taken to break
as little existing code as possible. "
so the answers are
1. New Zend Engine 2
2. Backward compatibility break
Take a look at ZendEngine-2.0.pdf. ToC
-------------------------------------------------------------------
Overview ................................................. 5
Revamped object model using object handles ............... 6
New Object Model Related Changes......................... 11
Additional Features...................................... 25
Multiple Inheritance .................................. 25
Private Member Variables .............................. 27
Static Class Member Variables ......................... 29
Exception handling (try/throw/catch) .................. 31
Revamped OO Syntax Overloading......................... 34
String offset syntax................................... 36
-------------------------------------------------------------------
And you say what this is not about OOP? When what about?
For hosting providers it is important, because OOP applications are
bigger and make more server load together with all features. But not
as important as second compatibility break. Despite of
"migrating your code from PHP
4 to 5 should be very easy. Most existing PHP 4 code should be ready
to run without changes, but you should still know about the few
differences and take care to test your code before switching versions
in production environments."
that means nothing more than a big pack of troubles for hosters. No
matter how minor is this break - it is not their job to mess with PHP
code of their customers on next major server upgrade and customers do
not want any more troubles with code, which already works. This is the
main factor that stops PHP 5 progress and not my desire to stick with
PHP 4 forever.
I do not know why am I arguing. It is useless anyways. =)
AD> True, PHP5 has improved OO support, but that doesn't mean
AD> that it hurts procedural style in any way.
I already explained how it hurts. No matter how minor is BC break if
it can cause working system failure.
AD> If you want more stable PHP version - update it regularly.
AD> Staying with DOS 6.22 and saying that you don't like those
AD> new OSes may be fine, but it doesn't make much sense to me..
Bad abstraction. DOS 6.22 is not deployed and used as widely as
PHP 4 at the moment.
>> Maybe you need to expand developers base somehow or make advanced
>> hot patch submission/review/approval/integration system on top of
>> chora, so less time will be wasted to review patch submissions.
AD> That still doesn't add much point to supporting 4 branches
AD> (4, 5.0, 5.1 & HEAD) in the same time.
Abandon 5.0 if 5.1 is stable. Remove PHP 4 together with PHP 3 into
archive. Make it clear PHP 4 isn't supported any more and make us
believe PHP 5 is good, stable way to go. You may start with
sourceforge.
AD> Actually I would object even if you want to do it yourself.
I'm not pretending.
WBR.techtonik
--
(B)uilding, (A)ntenna, (S)pan and (E)arth
* terminal velocity - 54m/s, 305m *
