ceo@l-i-e.com 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
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.
Excellent!
Now it just needs a ton of documentation at the 5.y point where it
goes in to explain how this feature that one generally associates with
the 6.x series works in 5.y but not in 5.(y-1) and we're all set...
Otherwise, we have to spend all our time answering questions about why
this script with the new stuff only sometimes works in PHP 5...
I think it's a great idea to provide the migration facility, but it's
GOT to be documented in big bold letters at whatever version it goes
"in" to avoid massive amounts of questions.
--
Some people have a "gift" link here.
Know what I want?
I want you to buy a CD from some starving artist.
http://cdbaby.com/browse/from/lynch
Yeah, I get a buck. So?