Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:30985
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 64.233.184.234 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:sender:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
        b=nqvlwKu2DllrZ3ODwPK+i+vi9rm3RxWrVmVIw3LOoBmaoKUSodMppohMnubBGLRFECrOHjxatKlHF6MA/w8zQDdcOxJQGpVo3eAV1q2KAEgBtBbT5YAHP/oR0JsdN09p5TYDcutLS9yTUst1SQ+9AUr/AXB3f4K0+45Ul5qu2T8=
Message-ID: <b5f7bf6c0707160910g286553a7rdc0aef25cce2c9e8@mail.gmail.com>
Date: Mon, 16 Jul 2007 12:10:41 -0400
Sender: david.coallier@gmail.com
To: jani.taskinen@iki.fi
Cc: "Antony Dovgal" <antony@zend.com>, "Lukas Kahwe Smith" <mls@pooteeweet.org>, 
	"Andi Gutmans" <andi@zend.com>, 
	"Ilia Alshanetsky" <ilia@prohost.org>, internals@lists.php.net
In-Reply-To: <1184599531.3352.22.camel@localhost.localdomain>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <698DE66518E7CA45812BD18E807866CE648191@us-ex1.zend.net>
	 <54C4340A-D9EA-4B5A-B39C-B55B29B1B3BC@prohost.org>
	 <698DE66518E7CA45812BD18E807866CE648193@us-ex1.zend.net>
	 <469B7FB1.1070507@pooteeweet.org> <469B8C73.8020908@zend.com>
	 <1184599531.3352.22.camel@localhost.localdomain>
Subject: Re: [PHP-DEV] POSIX regex
From: davidc@php.net ("David Coallier")

On 7/16/07, Jani Taskinen <jani.taskinen@sci.fi> wrote:
> Thank you Lucas and Antony. Could not agree more..
>
> On Mon, 2007-07-16 at 19:19 +0400, Antony Dovgal wrote:
> > Thank you Lukas for expressing exactly my thoughts on this.
> >
> > On 16.07.2007 18:24, Lukas Kahwe Smith wrote:
> > > Andi Gutmans wrote:
> > >> Even in PHP 6 I am not sure it's a good idea. There are a huge amount of
> > >> apps that use them and it'll be very hard for people to upgrade.
> > >> Anyway, let's do some more research on that once we get closer to PHP 6
> > >> and see what the migration path looks like. We'll have to check with a
> > >> few popular apps + google code search :)
> > >> No need to decide on that right now without having more info.
> > >
> > > I disagree with this approach. The thing is that we need to get a clear
> > > message out ASAP. This all ties into topics like if we will have a
> > > unicode off/on switch or not. Delaying these decisions will hurt our
> > > userbase. We need to prepare them early.
> > >
> > > IMHO we should use PHP6 as the clean up release. Drop unicode on/off
> > > switch, accept that the bulk of all code will need to be rewritten from
> > > scratch. The benefit will be that it will truely be cleaned up, people
> > > will still be able to leverage the bulk of their PHP programming
> > > background and they can enjoy the fastest possible unicode engine we can
> > > provide them.
> > >
> > > PHP5 will be for the people that cannot make the jump. We will back port
> > > whatever we can reasonably get into PHP5. People will linger on PHP5,
> > > just as they are doing now with PHP4. So it goes. At least we will not
> > > punish the early adopters for those that are unwilling to move to the
> > > new version in the near future anyways.
> > >
> > > At any rate .. the time is now to make a decision on what its gonna be.
> > > PHP6 with BC hacks or not.
> > >
> > > regards,
> > > Lukas
> > >
> >
> >
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

Another thing to mention is that without GLOBALS (PHP6), most
application and <cough>php4-developers</cough> will have far more
problems than without posix regex'es.


D