Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:69051
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain ez.no designates 213.199.154.12 as permitted sender)
To: Terence Copestake <terence.copestake@gmail.com>, Florin Patan
	<florinpatan@gmail.com>
CC: Arvids Godjuks <arvids.godjuks@gmail.com>,
	=?iso-8859-1?Q?Johannes_Schl=FCter?= <johannes@schlueters.de>,
	"internals@lists.php.net" <internals@lists.php.net>
Thread-Topic: [PHP-DEV] Wake up
Thread-Index: AQHOrtwWoZAGIoegV0KFP51RC1w4SZnAXi6AgAAd9wCAAAsXAIAAB3WAgAArDQA=
Date: Wed, 11 Sep 2013 16:27:05 +0000
Message-ID: <46D7B68A-7424-4924-82CE-939782D6C7CB@ez.no>
References: <CAA9esyT9vwOOk5AuyWNR7hDOJc=DHjZxPTpo370M_+tByoEmgA@mail.gmail.com>
 <CAL0xaBFxxJkeoSbzVY5iVc9FixjeoLjS-UF7GUZxq8BXHenQyg@mail.gmail.com>
 <1378903588.3917.54.camel@guybrush>
 <CAL0xaBFLV--dMfsOmOW2yxLdZFswG0DM+dVkqFoWoU4o4QQ7Gg@mail.gmail.com>
 <CAPMc8ua1DLrVm2NACKWanEO_nnEUzAqa0hwtf=gWpAGXRSv1fQ@mail.gmail.com>
In-Reply-To: <CAPMc8ua1DLrVm2NACKWanEO_nnEUzAqa0hwtf=gWpAGXRSv1fQ@mail.gmail.com>
Accept-Language: nb-NO, de-DE, en-US
Content-Language: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <3CC766A65A17D54DA394FA24571B87A9@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [PHP-DEV] Wake up
From: andre.romcke@ez.no (=?iso-8859-1?Q?Andr=E9_R=F8mcke?=)

On Sep 11, 2013, at 15:52 , Terence Copestake <terence.copestake@gmail.com>
 wrote:

> (.. ) a concern
> brought up repeatedly both here and in various blogs is the lack of
> direction or vision. There's a conflict between people who want to keep P=
HP
> simple and accessible and people who want to make PHP into a professional
> programming tool/environment, complete with all bells and whistles. With
> everyone wanting something different and having different ideas on who th=
e
> target users are, what PHP's responsibilities and concerns should be, etc=
.,
> it's going to be the classic struggle of trying to be everything for
> everybody all at once.


Won't solve the perceived lack of vision, but the conflict could potentiall=
y be solved by modeling php language standardization after how they do it a=
t Ecma, w3c or iso.
For instance: Let php-internals be as is, Internal stuff in PHP engine and =
announcements of rfc's for it, but move out the organization of standardizi=
ng the language.

1. The people involved in standardization should be representatives of the =
different implementations of PHP language.
2. Accepting changes to the language would requirer that at least one imple=
mentation have it working behind a compile/runtime flag*
3. Language Tests should be shared and be part of the standardization effor=
t
4. The PHP language standardization body should always allow some variation=
 on how much a implementation helps the user by default

    # Example: Argument and return type hinting**

    Specification on this can define two modes of operation:
        1. Fatal error on wrong type
        2. Strict error on type conversion, and Fatal error on type convers=
ion with data loss

    HPHP could then use mode 1 by default, while PHP uses 2 by default (and=
 2 with strict errors disabled in production).

This was not intended as a flame, best regards
Andr=E9 R.
eZ Systems



* For anyone involved in web development you might know how messy css vendo=
r prefixes made the web, forcing them to be behind compile/runtime flags wo=
uld avoid this
** Just an example, ignore the details please=