Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:73391
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain ajf.me designates 198.187.29.233 as permitted sender)
Content-Type: multipart/alternative; boundary="Apple-Mail=_974CA1D5-68F2-4EA0-A223-BDCD7B62B799"
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
In-Reply-To: <533089B5.7040504@anderiasch.de>
Date: Mon, 24 Mar 2014 19:41:40 +0000
Cc: "Ivan Enderlin @ Hoa" <ivan.enderlin@hoa-project.net>,
 internals <internals@lists.php.net>
Message-ID: <F0D2DC2D-8E0C-4912-9AC1-13C1F1387918@ajf.me>
References: <532FF7B9.5040700@hoa-project.net> <533089B5.7040504@anderiasch.de>
To: Florian Anderiasch <ml@anderiasch.de>
Subject: Re: [PHP-DEV] PHP Specification
From: ajf@ajf.me (Andrea Faulds)

--Apple-Mail=_974CA1D5-68F2-4EA0-A223-BDCD7B62B799
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


On 24 Mar 2014, at 19:38, Florian Anderiasch <ml@anderiasch.de> wrote:
> Another point is that PHP is evolving faster than ever in the past,
> release cycles are actually quite short - how can you "freeze" stuff =
and
> even begin to commit to a timeframe of even a few months to write down
> this spec. Then who decides what is working as intended and what is a =
bug?
>=20
> So yes, I don't think there'd be a lot of objection if someone =
magically
> delivered parts of a language spec that is accurate to the current
> release (let's say 5.6 for now) - but who will do it? PHP's design has
> always been "fix your own itch, commit it, and as long as it doesn't
> interfer too much, it's good=94

PHP 6 is a good opportunity. We=92ll have more than the usual year to =
work on it.

--
Andrea Faulds
http://ajf.me/





--Apple-Mail=_974CA1D5-68F2-4EA0-A223-BDCD7B62B799--