Hi!
The problem with ext/xmlrpc is that it relies on libxmlrpc-epi[1], which
looks abandoned. Even worse, we're bundling a modified 0.51[2], while
the latest version is 0.54.1[3]. This is exacerbated by the fact that
the system library is usually build against libexpat, but the bundled
library i
Hi!
> So unless a maintainer steps forward, it might be best to deprecate
> and/or unbundle ext/xmlrpc.
I think we need to do ask for a maintainer, and if nobody steps up,
declare it unsupported and unbundle.
--
Stas Malyshev
smalys...@gmail.com
--
PHP Internals - PHP Runtime Development Mail
On 09.01.2019 at 19:06, Stanislav Malyshev wrote:
>> So unless a maintainer steps forward, it might be best to deprecate
>> and/or unbundle ext/xmlrpc.
>
> I think we need to do ask for a maintainer, and if nobody steps up,
> declare it unsupported and unbundle.
We still have no official “Call f
On Wed, Jan 9, 2019 at 6:28 AM Christoph M. Becker
wrote:
> The problem with ext/xmlrpc is that it relies on libxmlrpc-epi[1], which
> looks abandoned. Even worse, we're bundling a modified 0.51[2], while
> the latest version is 0.54.1[3]. This is exacerbated by the fact that
> the system libra
Hi,
On Thu, Jan 10, 2019, 1:34 AM Sara Golemon On Wed, Jan 9, 2019 at 6:28 AM Christoph M. Becker
> wrote:
>
> > The problem with ext/xmlrpc is that it relies on libxmlrpc-epi[1], which
> > looks abandoned. Even worse, we're bundling a modified 0.51[2], while
> > the latest version is 0.54.1[3]
Hello everybody and happy new year
I was thinking to RFC the following union:
```
typedef IterableFactory = array | IteratorAggregate;
```
As you know, passing Iterators around is a bad idea because one can
accidentally end up using them concurrently. For example if one entity is
traversing the
