Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:35947
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
Date: Tue, 4 Mar 2008 07:40:03 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Message-ID: <698DE66518E7CA45812BD18E807866CE01506D61@us-ex1.zend.net>
Thread-Topic: [PHP-DEV] [RFC] Replace the flex-based scanner with an re2c [1] based lexer
Thread-Index: Ach925a0d0BLa6t9RnOJjeCOGpbtmgAMbXcg
References: <1706278209.20080302232134@marcus-boerger.de> <698DE66518E7CA45812BD18E807866CE01506D08@us-ex1.zend.net> <1245060809.20080304103839@marcus-boerger.de>
To: "Marcus Boerger" <helly@php.net>
Cc: <internals@lists.php.net>
Subject: RE: [PHP-DEV] [RFC] Replace the flex-based scanner with an re2c [1] based lexer
From: andi@zend.com ("Andi Gutmans")

> -----Original Message-----
> From: Marcus Boerger [mailto:helly@php.net]
> Sent: Tuesday, March 04, 2008 1:39 AM
> To: Andi Gutmans
> Cc: internals@lists.php.net
> Subject: Re: [PHP-DEV] [RFC] Replace the flex-based scanner with an
> re2c [1] based lexer
>=20
> This sounds like we are going to do the same mistake over and over and
> over
> again. Who is forcing a hard time line on us? Why are we late in the
> develoment I don't get it at all. We haven't done all steps that were
> on
> our radar for 5.3. Now that we finally found time to address this we
> should
> do it. Otherwise the consequence is just that we have to do a 5.4
> version
> immediately. What is the reason for that, who is more happy with a 5.3
> now?
> Are we a company that makes money with selling upgrades?

Actually you'd be surprised but for a company it's easier to have less
versions than more versions because you don't need to suddenly update &
QA all of your products again (one of the problems with supporting
open-source is too many versions :) Fortunately I can do what I think is
right for PHP disconnected from those kind of dependencies :)

No one is forcing a hard deadline but let's not behave like this is
something we can just sneak in especially when we don't deal with a huge
audience (multibyte) and make people believe we can do it quickly. I was
going off the premise which I thought everyone was on board with which
meant a Beta in Q1. If we are going to change that then let's be honest
with ourselves and suggest a new schedule which allows addressing the
issues and enough testing in order to make it into a stable PHP 5.3.

Andi