Re: [RFC] Starting 5.3
| From: | Pierre | Date: | Tue, 08 May 2007 08:13:15 +0000 |
| Subject: | Re: [RFC] Starting 5.3 | ||
| References: | 1 2 3 4 5 6 7 8 9 10 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-29307@lists.php.net to get a copy of this message | ||
On 5/8/07, Derick Rethans <derick@php.net> wrote:
On Mon, 7 May 2007, Stanislav Malyshev wrote:The point is to make local URL wrappers working, not only phar://. Stanislav and Tony have a point, writing a custom extension to fix a problem that we introduced is a bad idea and does not solve the problem for anyone else but phar. If phar will be bundled or not does not matter, this problem has to be solved anyway. --PierreWe will need it: - by the time of PHP 6I think this problem should be fixed not by killing PEAR and converting it to PHP extensions but by fixing PHP 6 and enabling PEAR to work. Let me agree with Greg here. We can not go back to the PHP 4.x way of bundling PEAR. It's a PITA for both the PEAR people and the RM. PHP 5 uses the phar, which works brilliantly. So the fix here is to make something *like* phar work with PHP 6 as well. If it was to be based on streams (which I think it can only be), then we *need* some way of marking this new user stream as being local in order for require and include to work on those. Making a hack in PHP to allow "phar://" streams to work is a bad idea, a C-extension can easily work here.