On 6-Sep-06, at 3:48 PM, Lukas Kahwe Smith wrote:
boots wrote:
Well, with unicode semantics enabled, many PHP applications that
have not been designed with PHP6+unicode in mind are likely to
break. On the other hand when semantics are off, those
applications may work just fine. The other reason could be that
unicode enabled PHP will be noticeably slower then the one
without it, so hosters to conserve system resources may only
enable it for people who actually need the functionality.
Well to me its still not clear how much code will remain working
with PHP6 given the confusing situation about E_STRICT,
deprecation, OO purity-changes.
Well, first of all there is plenty of very prevalent PHP4 code around
that makes very light use of objects and works without any changes on
PHP5 and even PHP6 without unicode semantics, I'd also wager that
vast majority of PHP 5 code will run with very little changes on PHP
6 without unicode. If it does not, I can tell you for certain that
there will be very little inclination for people to upgrade to PHP6,
it'd make PHP 5 adoption rate as abysmal as it maybe, seem rapid.
Maybe its more feasible to work on making it easier for people to
run different PHP versions on the same host. I am sure Sara has
some ideas :)
It is not extremely difficult to setup PHP as cgi or better yet as
FCGI on Apache or Lighttpd, extremely simple in the case of the
latter. Which is why I think it is not a bad idea to advocate
availability of different web server instances with different PHPs on
the same machine.
Ilia Alshanetsky
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
