Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:75914
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: softfail (pb1.pair.com: domain golemon.com does not designate 209.85.220.54 as permitted sender)
MIME-Version: 1.0
Sender: php@golemon.com
In-Reply-To: <2BAAF697-C78A-4728-B78D-E5674D2C2CEA@ajf.me>
References: <CAESVnVq5P26Yi=w1yF3ETBEPe+PwJdEAuJ3-8Yw5vsQBy7ofDw@mail.gmail.com>
	<CAE4D29D-ADF6-4C88-AF34-2E70B8477858@ajf.me>
	<CAESVnVp=_XFH6f4izETTiNbSXnxgr0P_Cz2QKRemSr_orwfsEg@mail.gmail.com>
	<53CEE7A8.6030607@garfieldtech.com>
	<D8C4A859-569B-4B6A-91F7-E6CDE1952BB1@ajf.me>
	<CAESVnVo+V8qQnvxfhaT8nwGL495JHu08WhdU9z7h0nLERbqrJQ@mail.gmail.com>
	<2BAAF697-C78A-4728-B78D-E5674D2C2CEA@ajf.me>
Date: Tue, 22 Jul 2014 16:01:56 -0700
Message-ID: <CAESVnVrC1AtdgAYh8Noo7dveRnzNwqLctDMD7Wp_dFB3PBHLhg@mail.gmail.com>
To: Andrea Faulds <ajf@ajf.me>
Cc: Larry Garfield <larry@garfieldtech.com>, PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] PHP Language Specification
From: pollita@php.net (Sara Golemon)

On Tue, Jul 22, 2014 at 3:56 PM, Andrea Faulds <ajf@ajf.me> wrote:
> Ah, I think you misunderstand. What I mean is that we
> should only propose RFCs which change the spec
> when there is already a working implementation first.
> Otherwise, we might add things to the spec which won=E2=80=99t
> or can=E2=80=99t get implemented. It would also be best to propose
> changes which have been implemented in Zend, to ensure
> there is one fully compliant implementation.
>
Our RFCs tend to have implementations attached to them (in someone's
personal fork).  IMO we should make creating the spec PR part of the
RFC acceptance process, and that they should be landed together.  I
agree it doesn't make much sense to define unimplemented behavior as
the standard.