Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:75913 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 32758 invoked from network); 22 Jul 2014 22:56:54 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 22 Jul 2014 22:56:54 -0000 Authentication-Results: pb1.pair.com header.from=ajf@ajf.me; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=ajf@ajf.me; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain ajf.me designates 192.64.116.200 as permitted sender) X-PHP-List-Original-Sender: ajf@ajf.me X-Host-Fingerprint: 192.64.116.200 imap1-2.ox.privateemail.com Received: from [192.64.116.200] ([192.64.116.200:50344] helo=imap1-2.ox.privateemail.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 88/3A-21666-43CEEC35 for ; Tue, 22 Jul 2014 18:56:53 -0400 Received: from localhost (localhost [127.0.0.1]) by mail.privateemail.com (Postfix) with ESMTP id 6D156B0007B; Tue, 22 Jul 2014 18:56:50 -0400 (EDT) X-Virus-Scanned: Debian amavisd-new at imap1.ox.privateemail.com Received: from mail.privateemail.com ([127.0.0.1]) by localhost (imap1.ox.privateemail.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id n0CIVYRLIHhp; Tue, 22 Jul 2014 18:56:50 -0400 (EDT) Received: from [192.168.0.15] (unknown [90.210.122.167]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.privateemail.com (Postfix) with ESMTPSA id 88F50B00085; Tue, 22 Jul 2014 18:56:46 -0400 (EDT) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) In-Reply-To: Date: Tue, 22 Jul 2014 23:56:29 +0100 Cc: Larry Garfield , PHP internals Content-Transfer-Encoding: quoted-printable Message-ID: <2BAAF697-C78A-4728-B78D-E5674D2C2CEA@ajf.me> References: <53CEE7A8.6030607@garfieldtech.com> To: Sara Golemon X-Mailer: Apple Mail (2.1878.6) Subject: Re: [PHP-DEV] PHP Language Specification From: ajf@ajf.me (Andrea Faulds) On 22 Jul 2014, at 23:48, Sara Golemon wrote: > On Tue, Jul 22, 2014 at 3:41 PM, Andrea Faulds wrote: >> On 22 Jul 2014, at 23:37, Larry Garfield = wrote: >>> The big question here, though, is whether, going forward, we'll be >>> able to mentally switch to a "spec first" mentality. If not, the = spec will >>> get out of date and become less than useful. I hope we're able to >>> make that transition. >>=20 >> I think that=92s unrealistic. It will always be Zend code first, spec = second. >> HHVM can play catch-up ;) >>=20 > I dunno, with syntax changes being 2/3rd majority and our formal RFC > process in place, I think we (PHP) can reasonably learn to make > updating the spec a formal part of our process. 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=92t or can=92t get implemented. It would also be best to propose = changes which have been implemented in Zend, to ensure there is one = fully compliant implementation. -- Andrea Faulds http://ajf.me/