hi, On Tue, Sep 11, 2012 at 1:41 PM, Anthony Ferrara <ircmax...@gmail.com> wrote: > It's not the end of the world, because we can copy/paste that function into > the PECL extension, and just conditionally include it. There would be > duplication between the two, but it wouldn't be too bad...
agreed. > Consider? Sure. But I'm not sure it's worth while. Stas brought up the > adoption point, which I think is the kicker. The target audience for this > API is not the type that usually has access to install PECL extensions. So > while some may use it as an extension, the majority who would significantly > benefit from it wouldn't be able to. So the benefit to releasing it as a > PECL extension would basically defeat the point... > > And to Stas's point about the PHP solution not being the same, I fail to > understand why. It's built using identical algorithms (translated from C to > PHP as best as possible). It's tested using the same tests with the only > difference surrounding error messages. Plus it's portable (can be used on > shared hosts). The only real difference is testing the PHP version doesn't > say anything to the *security* of the C version. But it does test the API > and the concept... distros will provide it and that's the kicker. Believe, in the beginning of the new ext/zip, having it pecl drastically improve the adoption through distros. Less now as we have frequent PHP releases (also why I do much more less pecl releases ;). Cheers, -- Pierre @pierrejoye | http://blog.thepimp.net | http://www.libgd.org -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
