Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:53349
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 67.192.241.123 as permitted sender)
Message-ID: <4DFA7EDF.5050802@sugarcrm.com>
Date: Thu, 16 Jun 2011 15:08:31 -0700
Organization: SugarCRM
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10
MIME-Version: 1.0
To: PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [RFC] 5.4 features for vote (long)
From: smalyshev@sugarcrm.com (Stas Malyshev)

Hi!

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:

a. It is clear to everybody what is being proposed. If you have any 
doubts or see that it needs further discussion, please tell.

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.

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.

So here goes the big list:

1. Declare PHP/php reserved namespace name, not to be used in any user 
code. Does not require any code change, only documentation changes.

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.

3. Add E_STRICT to E_ALL. Nuff said. We did it in 6.0/unicode branch but 
didn't backport it.

4. Drop magic quotes. We've deprecated them in 5.3, we can kill them in 
5.4. See the RFC for fine details.

5. Binary notation for ints (0b10101). Same as 0x, but in binary. Python 
has it, we could too :)

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.

7. "Disable POST data processing" INI option.
Assigned: Gustavo Lopes

8. Cli web server. Built-in mini-HTTP server run directly from PHP binary.
Assigned: Moriyoshi Koizumi

9. Session Handlers class. A class that implements current session 
handler and can be extended with user code, fully or partially.
Assigned: Arpad Ray

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

-- 
Stanislav Malyshev, Software Architect
SugarCRM: http://www.sugarcrm.com/
(408)454-6900 ext. 227