Re: PHP 5.3 Suggested Feature List
| From: | Antony Dovgal | Date: | Sun, 09 Sep 2007 19:45:14 +0000 |
| Subject: | Re: PHP 5.3 Suggested Feature List | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-32139@lists.php.net to get a copy of this message | ||
On 09.09.2007 21:07, Ilia Alshanetsky wrote:
> Its been about a week since RFS for features to go into 5.3 has gone
> out and while there was not a "flood" of ideas there is a substantial
> list of key changes people would like to go into this release. I've
> compiled a list of all of the suggestions I've received, they are
> listed below in a form that will hopefully make it easy for people to
> vote their yeys and nays. My hope that we can reach an agreement
> within 1-2 weeks so 5.3 can be branched and work on it can begin.
>
> List of Feature Ideas
> ----------------------------
>
> 1) Backport the namespaces patch for PHP 6
>
> 1 0 -1
I thought most of us agreed that 5.3 should be == (PHP6 - Unicode).
1
> 2) Symlink the intl extension from PECL, but leave it disabled by
> default as is the case with all extensions dependent on external libs
>
> 1 0 -1
Once it's ready for production - why not?
1
> 3) Apply the Late Static Binding Patch
>
> 1 0 -1
0
> 4) Implement David's Circular Garbage collection patch
>
> 1 0 -1
IIRC that's one of the reasons for 5.3 branch.
1
> 5) Implement Sqlite3 support via the ext/sqlite extension (patch is
> already available)
>
> 1 0 -1
0/-1 (see on reason to touch a working extension, but I don't really care).
> 6) Remove safe_mode, register_globals and magic_quotes
>
> 1 0 -1
Let's leave this for HEAD.
-1
> 7) Introduce mysqlind library into core and use it as a backend for
> PDO and mysqli extensions (possibly enabling them by default)
>
> 1 0 -1
1
Same as PECL/intl - once it's ready, I see no reason to keep it "hidden".
> 8) OpenID enabling patch for OpenSSL and PHP 5
>
> 1 0 -1
0
> 9) Add array_replace[_recursive] functions (patch is already available)
>
> 1 0 -1
Do we really need more array functions?
I believe we already have quite a number.
-1
> 10) Split off deprecation from E_STRICT into E_DEPRECATED
>
> 1 0 -1
-1
Didn't see any arguments for this.
> 11) Merge the zend_arg_info const'ify patch
>
> 1 0 -1
0
> 12) Merge the GCC 4 -fvisibility patch
>
> 1 0 -1
0
> 13) Switch for disabling/enabling materialized cursors in mysqli
>
> 1 0 -1
0
> 14) Link phar extension from PECL into core (possibly enabling it by
> default)
>
> 1 0 -1
0 (-1 for enabling it by default).
> 15) Merge Matt's ZEND_SIGNED_MULTIPLY_LONG() optimization patch
>
> 1 0 -1
From what I recall, all Matt's patches were really good.
So I'm 0/+1.
> 16) Introduce new php.ini files parser/scanner + CGI/FastCGI?
> "htaccess" style ini file support
>
> 1 0 -1
0
AFAIK it's too early.
> 17) Merge __callStatic patch from PHP 6
>
> 1 0 -1
1/0.
I believe we should decide on more general problems first,
i.e. what is 5_3 - is this (5_2 + a couple of patches) or (HEAD - Unicode)?
> 18) Introduce concept of "strict classes" that do not permit dynamic
> property creation
>
> 1 0 -1
0
--
Wbr,
Antony Dovgal