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, the
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 ar
emo wrote:
>> 14) Link phar extension from PECL into core (possibly enabling it by
>> default)
>>
>> 10-1
>
> +1 (Depends how it will cope with namespaces?)
??
Perhaps you're thinking of different code? pecl/phar is unaffected by
any changes to the PHP language syntax. Its sole
My bad, please ignore the comment.
Thanks Greg.
Regards,
Emil Ivanov
Gregory Beaver wrote:
emo wrote:
14) Link phar extension from PECL into core (possibly enabling it by
default)
10-1
+1 (Depends how it will cope with namespaces?)
??
Perhaps you're thinking of different co
Ilia Alshanetsky wrote:
> 1) Backport the namespaces patch for PHP 6
+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
0 (didn't see anything relevant of it yet)
> 3) Apply the Late Static Binding Patch
12) Merge the GCC 4 -fvisibility patch
-1 (eventually make it a configure option first? PHP is a API mess)
The patch is safe because otherwise PHP wouldn't work on windows (as windows
doesn't export the symbols by default).
Nuno
--
PHP Internals - PHP Runtime Development Mailing List
To uns
