That's fair enough, so long as the older version is readily available.
It
becomes a problem if it isn't. The word 'replace' kind of intimates
that
the original extension is effectively a goner - and if you meant
'replace in
the core', I'm unaware of a precedent for that.
Yes.
Yes what?
On Mon, 2005-08-29 at 14:43 +0200, Steph wrote:
Yes.
Yes what? :)
'replace in core'
John
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
[EMAIL PROTECTED]
Cc: Rasmus Lerdorf [EMAIL PROTECTED]; internals@lists.php.net;
[EMAIL PROTECTED]
Sent: Sunday, August 28, 2005 3:42 AM
Subject: Re: [PHP-DEV] Re: PHP 5.1: Does it still require ext/xmlrpc for
pear?
On that line though, I'd like to finish up the ext/xmlrpci ext I've got
in PECL
At 16:23 28.08.2005, you wrote:
'Replace'? Code written for ext/xmlrpc won't work with ext/xmlrpci. Will
ext/xmlrpc be available in PECL, given that it doesn't appear to have an
active maintainer?
I'm well aware of ext/xmlrpc's limitations, haven't tried the new (but
necessary) pecl/xmlrpci
PROTECTED]
Cc: Rasmus Lerdorf [EMAIL PROTECTED]; internals@lists.php.net;
[EMAIL PROTECTED]
Sent: Sunday, August 28, 2005 3:42 AM
Subject: Re: [PHP-DEV] Re: PHP 5.1: Does it still require ext/xmlrpc for
pear?
On that line though, I'd like to finish up the ext/xmlrpci ext I've got
in PECL
On Sat, 27 Aug 2005, Rasmus Lerdorf wrote:
Jani Taskinen wrote:
If I understood correctly, the fixed XML_RPC pear package
was updated to the PHP_5_1 branch already. Why is ext/xmlrpc
still required?
It isn't.
Ok. Fix committed. :)
--Jani
--
PHP Internals - PHP
On that line though, I'd like to finish up the ext/xmlrpci ext I've got
in PECL and replace ext/xmlrpc. It'll eliminate the custom lib we have
for that ext, ground-up designed for PHP 5 (ext/soap style overloading,
etc.) Objections?
Cheers,
John
On Sun, 2005-08-28 at 04:10 +0300, Jani Taskinen
