On Wed, 2014-10-01 at 14:26 +0200, Ferenc Kovacs wrote:
> On Tue, Sep 30, 2014 at 10:18 PM, guilhermebla...@gmail.com <
> guilhermebla...@gmail.com> wrote:
>
> > > What does that even mean?
> >
> > It means that any new functionality that gets into core could be considered
> > "young". Like when PHAR got introduced, it was a "young" extension. Same
> > for PDO, same for FileInfo...
> > What I'm trying to highlight is that being a recently coded extension or
> > not, it's not a good argument to say join/no join.
> >
>
> phar is a really bad example, the maintainers left right after it was
> accepted into the core making it a really bad technical burden, as it
> tightly integrated into the streams handling and stuff, making it a
> liability.
> from the average user POV I think it would be a bit weird why do we add a
> relatively new package which is at the bottom of the download stats (
> http://pecl.php.net/package-stats.php) while not bundling stuff like
> memcache or mongo which are both mature and used/required by much more
> people/project.
> personally I think that a pecl extension needs to have stronger arguments
> to be bundled with php-src than the fact that it would probably create a
> bit more exposure for the ext.
>
Afternoon,
I think you got your answer anyway, so this message might fall on
deaf ears.
The assertion that there is no way to use mutex in a cross platform
way in PHP is actually wrong: http://php.net/mutex
The number of people that should be using mutex directly in PHP is
about 4. PHP programmers are ill prepared for using such things, making
some code exist, doesn't prepare anyone.
With a quick glance, there is a number of mistakes in the code.
There is an incorrect assumption that what this is doing is safe, it
is not.
You cannot share a mutex across process boundaries without setting
attributes on creation, this includes forked child processes; given
PHP's normal mode of execution does involve forking and
multi-processing, the ideas in this extension are very close to useless.
If this extension were well written and had all bases covered it
still wouldn't make sense to include it, handing over synchronization to
userland simply will not work.
So, as you might have guessed, a "-1, and your barking mad" from me.
Cheers
Joe
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
