Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:30999
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain zend.com designates 63.205.162.114 as permitted sender)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 17 Jul 2007 08:07:19 -0700
Message-ID: <698DE66518E7CA45812BD18E807866CE6483EC@us-ex1.zend.net>
Thread-Topic: [PHP-DEV] POSIX regex
Thread-Index: AcfIgdiyyutzdjEKRQiiv5JQmruiiAAAYSmQ
References: <698DE66518E7CA45812BD18E807866CE648191@us-ex1.zend.net> <54C4340A-D9EA-4B5A-B39C-B55B29B1B3BC@prohost.org> <698DE66518E7CA45812BD18E807866CE648193@us-ex1.zend.net> <469B7FB1.1070507@pooteeweet.org> <698DE66518E7CA45812BD18E807866CE648290@us-ex1.zend.net> <469C6436.2060009@pooteeweet.org> <698DE66518E7CA45812BD18E807866CE6483DF@us-ex1.zend.net> <469CD717.2070607@pooteeweet.org>
To: "Lukas Kahwe Smith" <mls@pooteeweet.org>
Cc: "Ilia Alshanetsky" <ilia@prohost.org>,
	<jani.taskinen@iki.fi>,
	<internals@lists.php.net>
Subject: RE: [PHP-DEV] POSIX regex
From: andi@zend.com ("Andi Gutmans")

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=3Doff 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=20
(unciode_semantics=3Don). 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:mls@pooteeweet.org]=20
> Sent: Tuesday, July 17, 2007 7:50 AM
> To: Andi Gutmans
> Cc: Ilia Alshanetsky; jani.taskinen@iki.fi; internals@lists.php.net
> Subject: Re: [PHP-DEV] POSIX regex
>=20
> Andi Gutmans wrote:
>=20
> > Here's my proposed way of figuring how to make migration=20
> easier. Port=20
> > the following applications to PHP 6 and let's see what we can learn=20
> > from
> > it:
> > - mediaWiki
> > - SugarCRM
> > - Drupal
> > - Wordpress
>=20
> IIRC Wordpress is a good example of bad source code to fix.=20
> Drupal would be a good example of a PHP4 style fairly=20
> procedural app to port.=20
> mediaWiki also seems like a worthy cause since its one of=20
> those apps that would actually benefit quite a bit from=20
> unicode support, but I guess you are talking about porting=20
> with unicode=3D=3Doff, right?
>=20
> SugarCRM would be a good example of a gigantic horrible=20
> horrible source code to fix and I am not sure if I would put=20
> it on the list considering the limited open source release=20
> they do. I think it would be cool of they would do it=20
> themselves or sponsor whoever is doing it.
>=20
> We also have an SoC project where someone is implementing a=20
> PHP6 version of Jaws.
>=20
> regards,
> Lukas
>=20