[EMAIL PROTECTED] wrote:
On Tue, November 14, 2006 3:08 pm, Sara Golemon wrote:
How many applications out there aren't taking advantage of things like
property visibility in PHP5 because they want to remain compatable
with
the myriad PHP4 installations? How much are compromises like that
slowing PHP5 adoption?
How many sysadmins and other decision-makers out there aren't adopting
PHP5.x, much less 6.x, because we've changed too many things too
quickly in BC-incompatible ways?
*THAT* is what is slowing the adoption rate, not the applications
developers not WANTING to use the better code.
It's the fact that one cannot easily migrate code.
And while it's trivial for some to set up 5 on another machine and
proxyhost or whatever, for many folks, that's not really an option.
I didn't even read the patch, but unless it's guaranteed NOT to break
anything at all in php4 (yes, 4, not 5):
-1
I agree with you 100%. You didn't read the patch.
This isn't introducing a BC break, it's lessening the severity of one
that already exists.
And yes, I /can/ guarantee that it won't break existing scripts.
-Sara
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
