Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:75905
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 108.166.43.67 as permitted sender)
Message-ID: <53CEE5A4.6080701@sugarcrm.com>
Date: Tue, 22 Jul 2014 15:28:52 -0700
Organization: SugarCRM
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Sara Golemon <pollita@php.net>, 
 PHP internals <internals@lists.php.net>
References: <CAESVnVq5P26Yi=w1yF3ETBEPe+PwJdEAuJ3-8Yw5vsQBy7ofDw@mail.gmail.com>
In-Reply-To: <CAESVnVq5P26Yi=w1yF3ETBEPe+PwJdEAuJ3-8Yw5vsQBy7ofDw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] PHP Language Specification
From: smalyshev@sugarcrm.com (Stas Malyshev)

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.

> 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.

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.
-- 
Stanislav Malyshev, Software Architect
SugarCRM: http://www.sugarcrm.com/