Re: Moving COM, Socket & mhash to PECL

Hello, On 12/8/06, Ilia Alshanetsky <ilia@prohost.org> wrote:

This is an exploratory e-mail, so don't panic just yet :-). I am thinking of moving the COM, mhash and socket extensions to PECL in 5.2 and 6.0 releases and was hoping to hear for & against arguments. The reason for the making this move are as follows: COM:

        Un-maintained at this time and has a fairly serious number of bugs

(26 by latest count, many of which are crashes)

It has a lot of bugs yes, but it is useful and works well for many situations. I do not like the idea to move it out of php.

        Moving it to PECL will allow for an independent release cycle, which

may allow for faster fix deployment etc...

It is possible without moving it out. It could even be a good thing to do it.

        I hoping the move will encourage people and/or companies to start

maintaining the extension.

There is bugs and it is expected, COM allows a lot of things with a lot of external apps, no wonder. But it works well (for what I did at least, office, IE and XML com). I can try to take a look at the open bugs if Wez is missing the time.

mhash:

        Everything this extension that relies on an external lib to do, is

already done by hash extension that is enabled by default and requires no external libs. There is simply no reason to keep it around.

We may move it from php 6.0 and up or at least from 5.3.0.

sockets:

        Un-maintained.
        Majority of what it can do can already by done via streams in a much

more consistent and stable fashion.

+1 from php 6.0 and up but I'm worrying a bit about 5.x code relying on it. --Pierre