Re: Latest commit -- depreciation of call_user_method()
| From: | Jani Taskinen | Date: | Fri, 18 May 2001 15:50:18 +0000 |
| Subject: | Re: Latest commit -- depreciation of call_user_method() | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-55789@lists.php.net to get a copy of this message | ||
On Fri, 18 May 2001, Rasmus Lerdorf wrote:
>> Ah. I must have been dreaming then.. :)
>> I remember that someone submitted some bug report about this very issue.
>>
>> Anyway, now I see that there really is good reason having that
>> version (PHP_#ext#_API_NO ?) after all. And having that..we should
>> propable start moving those extensions one by one into PEAR?
>
>That has been the plan for a while now. Not necessarily moving all the
>optional extensions, but some of them. And new fringe extensions would go
>straight to PEAR.
Too bad it seems not to be going anywhere..
>> And btw. Why not have a function in PHP core that can be used to get the
>> desired extensions remotely from pear.php.net? If we have a
>> PHP_#ext#_API_NO, running a 'update_php_extensions()' would
>> go and grab the updated (if the extension HAS been updated) one..etc..
>> (I'm just thinking out loud..ignore me :)
>
>There is the start of a set of command line tools for doing this.
I don't think having those separately is a good idea.
More like a function set in PHP would make more sense.
As you have to have the core PHP anyway?
--Jani