Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:75917
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.219.48 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <53CEE5A4.6080701@sugarcrm.com>
References: <CAESVnVq5P26Yi=w1yF3ETBEPe+PwJdEAuJ3-8Yw5vsQBy7ofDw@mail.gmail.com>
	<53CEE5A4.6080701@sugarcrm.com>
Date: Tue, 22 Jul 2014 19:19:12 -0700
Message-ID: <CAKOpQSxFYrTtZpUSoq5QKpV-2-Kck9Eu4WkKxz0CZ0kuJ=nJqg@mail.gmail.com>
To: Stas Malyshev <smalyshev@sugarcrm.com>
Cc: Sara Golemon <pollita@php.net>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=089e013d080047d94304fed2f7b1
Subject: Re: [PHP-DEV] PHP Language Specification
From: kris.craig@gmail.com (Kris Craig)

--089e013d080047d94304fed2f7b1
Content-Type: text/plain; charset=UTF-8

On Tue, Jul 22, 2014 at 3:28 PM, Stas Malyshev <smalyshev@sugarcrm.com>
wrote:

> Hi!
>
> > To that end, we (as in Facebook), have been putting together a formal
> > language spec for PHP (using PHP 5.6 as the source of truth) along
> > with an additional conformance test suite (which compliments
> > Zend/tests).  We've talked to some engine folks along the way to get
> > feedback and make version 1 as good as it can be, and we're really
> > close to releasing it (aiming for next week).  Note that this document
> > only covers the language syntax and not the standard runtime library.
>
> Thank you Sara and Facebook team for doing something we've been talking
> about for more than a decade and before that nobody actually attempting
> to do. I think it is a great development and I hope to see the first
> version soon.
>

+1


>
> > This document is meant for PHP, and PHP should be the steward of it
> > going forward, so we (as in PHP) should start looking at good ways to
> > keep it up to date and revise it over time.  As a sneak-peak, uploaded
> > a very small section so that you get an idea for what the
> > document looks like overall.
>
> I would propose choosing some collaborative platform for managing it,
> something like Google Docs (suggestions about best platform ever for
> that are welcome :) so that people could comment on specific parts and
> keep track of what is the current state and what has been discussed.
>

+1


>
> Alternatively, we could do a wiki maybe but the problem there is that it
> is hard to export (unless anybody knows wiki setups that can be easily
> exported into single document).
>
> I'd also advocate creating a workgroup and a mailing list for it to
> discuss the spec and to work on it and other things like ones above there.
>

+1


> --
> Stanislav Malyshev, Software Architect
> SugarCRM: http://www.sugarcrm.com/
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--089e013d080047d94304fed2f7b1--