Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:31050
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.146.178 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=lpi5KazRTCrP3qurvJ2iKwa7ndZvuCTyb5N2PrLGUeQmJvk5mwSFQtZc6IeNJ/XQQaNE09FzbJDdwp1MktKGDdtpgP6seAgpfkprJsJwDULZqA93+YgB6p1cNIvhK6lA/cT5OyQss/Z6czMGOCODe0xpMTPw9dsK68zyZwpdqAo=
Message-ID: <fe05d1540707180453l24d66753u5c2e4ab0c4283d29@mail.gmail.com>
Date: Wed, 18 Jul 2007 13:53:45 +0200
To: "Lukas Kahwe Smith" <mls@pooteeweet.org>
Cc: "Zeev Suraski" <zeev@zend.com>, "Andi Gutmans" <andi@zend.com>, 
	"Ilia Alshanetsky" <ilia@prohost.org>, jani.taskinen@iki.fi, 
	internals@lists.php.net
In-Reply-To: <469DFDEC.6020903@pooteeweet.org>
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>
	 <698DE66518E7CA45812BD18E807866CE648290@us-ex1.zend.net>
	 <fe05d1540707170021y423f7d81kd1ab28a5719630fb@mail.gmail.com>
	 <7.0.1.0.2.20070718023255.0dc0eed0@zend.com>
	 <469DFDEC.6020903@pooteeweet.org>
Subject: Re: [PHP-DEV] POSIX regex
From: pierre.php@gmail.com (Pierre)

On 7/18/07, Lukas Kahwe Smith <mls@pooteeweet.org> wrote:
> Zeev Suraski wrote:
>
> > Finally, at the risk of sounding like a broken record, we always need to
> > remember that BC breakage accumulates, and it's not binary.  Every
> > cleanup we do in PHP 6 will further slow migration, and as Andi pointed
> > out a few days ago, things don't look too well as it is.
>
> Agreed, its not binary, but its also not the simple addition of all
> issues either. The effort does diminish as you can cover multiple BC
> breaks in one going over your code. The key thing that we screwed up
> with PHP 5.x was not providing enough documentation on the BC breaks.
> Doing this better this time (the migration guides are a good start,
> porting some major apps and documenting the issues is another) could
> help us easy the transition as well. But as you point out, there is the
> fixed overhead of having to do the QA'ing at any rate.

What we really screwed up are the breakages _after_ 5.0, between 5.0
and now. Every one expects changes and breakages between two major
major versions, no matter the language.

--Pierre