Hmm I don't quite understand what bad code vs. good code plays here. Wordpress is one of the most popular applications out there so it's got huge value to our community. I bet there's a huge amount of PHP applications who's source code is of the same quality or worse. Anyway, the issues I have seen would also be relevant to what you call "good" code but again, when it comes to compatibility, I don't quite know why that will play a big role.
I am talking about porting to both unicode_semantics=off and on. This will give us a good understanding of the difference of the modes and where we're at. I bet most people who are voicing their opinions have actually not tried to write a sizeable application with PHP 6 and also tried to run an existing one on PHP 6 (unciode_semantics=on). I can also do some performance testing in our performance lab once we have both working. I haven't yet mentioned how companies building high-performance sites would probably take a huge hit by moving to Unicode to the point where I think they will not adopt for a long time and then will be faced with the choice to migrate off of PHP or bite the bullet. With some of the companies I know that have huge server farms adding 50% capacity (or whatever the number is) could be a good enough reason to migate off as they are paying huge fees for the servers... Andi > -----Original Message----- > From: Lukas Kahwe Smith [mailto:[EMAIL PROTECTED] > Sent: Tuesday, July 17, 2007 7:50 AM > To: Andi Gutmans > Cc: Ilia Alshanetsky; [EMAIL PROTECTED]; internals@lists.php.net > Subject: Re: [PHP-DEV] POSIX regex > > Andi Gutmans wrote: > > > Here's my proposed way of figuring how to make migration > easier. Port > > the following applications to PHP 6 and let's see what we can learn > > from > > it: > > - mediaWiki > > - SugarCRM > > - Drupal > > - Wordpress > > IIRC Wordpress is a good example of bad source code to fix. > Drupal would be a good example of a PHP4 style fairly > procedural app to port. > mediaWiki also seems like a worthy cause since its one of > those apps that would actually benefit quite a bit from > unicode support, but I guess you are talking about porting > with unicode==off, right? > > SugarCRM would be a good example of a gigantic horrible > horrible source code to fix and I am not sure if I would put > it on the list considering the limited open source release > they do. I think it would be cool of they would do it > themselves or sponsor whoever is doing it. > > We also have an SoC project where someone is implementing a > PHP6 version of Jaws. > > regards, > Lukas > -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
