Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:53384
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain mozo.jp from 209.85.210.42 cause and error)
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <4DFA7EDF.5050802@sugarcrm.com>
Date: Mon, 20 Jun 2011 20:31:22 +0900
Cc: PHP Internals <internals@lists.php.net>
Content-Transfer-Encoding: quoted-printable
Message-ID: <B5D22F5C-2F1E-4256-A01D-5EA1260533C7@mozo.jp>
References: <4DFA7EDF.5050802@sugarcrm.com>
To: Stas Malyshev <smalyshev@sugarcrm.com>
Subject: Re: [PHP-DEV] [RFC] 5.4 features for vote (long)
From: mozo@mozo.jp (Moriyoshi Koizumi)

Hi,

I've been pretty busy for a while, and didn't well keep up to =
discussions regarding my built-in server patch.  Is there any agreement =
on it yet?

Moriyoshi

On 2011/06/17, at 7:08, Stas Malyshev wrote:

> Hi!
>=20
> Below is the list of the features proposed for inclusion in 5.4, as =
outlined in https://wiki.php.net/todo/php54. Please read the TODO page =
and the RFCs linked there for details.
> This mail is not a vote call but rather description of things that =
will be put to vote soon. For each one, I'd like to see that:
>=20
> a. It is clear to everybody what is being proposed. If you have any =
doubts or see that it needs further discussion, please tell.
>=20
> b. We didn't miss something. If you have a proposal that has RFC in =
good shape, patch (or can have patch within 1 month from now) and you =
think has to be in 5.4 and has good chance for community support, please =
tell.
>=20
> c. For proposals that have assigned developers, I'd like for them to =
ensure they still want these proposals in and commit to doing the work =
in time for 5.4 beta (~end of July). It's no point to vote on a feature =
if the developer responsible for it won't have time or desire to =
implement it.
> If the proposal doesn't have anybody assigned, that means I can do it =
if needed - though of course I'd be glad if somebody else would do it =
too.
>=20
> So here goes the big list:
>=20
> 1. Declare PHP/php reserved namespace name, not to be used in any user =
code. Does not require any code change, only documentation changes.
>=20
> 2. Make primitive type names reserved words (in case we ever want some =
form of scalar typing or anything else with scalar types). Using them as =
identifiers would return parse error for now. May have BC implications.
>=20
> 3. Add E_STRICT to E_ALL. Nuff said. We did it in 6.0/unicode branch =
but didn't backport it.
>=20
> 4. Drop magic quotes. We've deprecated them in 5.3, we can kill them =
in 5.4. See the RFC for fine details.
>=20
> 5. Binary notation for ints (0b10101). Same as 0x, but in binary. =
Python has it, we could too :)
>=20
> 6. Array shortcuts. Make [ 'blah', 'blah' ] work same as array('blah', =
'blah'), etc. Does not include any new JSON-like syntax, etc. - just =
making '[' be 'array(' and ']' be ')' in that context.
>=20
> 7. "Disable POST data processing" INI option.
> Assigned: Gustavo Lopes
>=20
> 8. Cli web server. Built-in mini-HTTP server run directly from PHP =
binary.
> Assigned: Moriyoshi Koizumi
>=20
> 9. Session Handlers class. A class that implements current session =
handler and can be extended with user code, fully or partially.
> Assigned: Arpad Ray
>=20
> 10. Callback type check in arguments. Type check in method calls same =
as 'array' or 'MyClass' type checks but would match valid callbacks.
> Assigned: Hannes Magnusson
>=20
> --=20
> Stanislav Malyshev, Software Architect
> SugarCRM: http://www.sugarcrm.com/
> (408)454-6900 ext. 227
>=20
> --=20
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>=20