I think waiting until PHP++ is probably the best approach. It would've been nice to have the current libcurl version in 5.4.0, but since we're not talking about any critical bug/security fixes, I don't think it's that big a deal either way. So we may as well just sit on it for now.
--Kris On Sun, Mar 11, 2012 at 8:55 PM, Pierrick Charron <pierr...@webstart.fr>wrote: > I thought about it but I think it may confuse people to have two > different extensions with the same name, same interface, but one in > pecl and one in the core package (the difference between the 2 > versions are not that big). Also as ilia mentioned if someone already > have the original version, they will have symbol conflicts. So I guess > we could just wait until PHP next unless someone have an other nice > solution which will not confuse people :) > > Thanks all for your input. > > Pierrick > > On 11 March 2012 03:33, Stas Malyshev <smalys...@sugarcrm.com> wrote: > > Hi! > > > > > >> I wanted to make this new version available in PHP5.4 but > >> unfortunately I did finish my work when it was already in RC phase. > >> The question now is should we include this new version in PHP5.4.1 or > >> should we wait for PHP 5.5/6/7 or whatever PHP next will be. There is > >> no feature break (AFAIK) so all the previous code should work as > >> expected. You'll find the list of new features attached and the last > >> code in the trunk branch. > > > > > > Can't you make it also available as pecl extension, which could be built > on > > 5.4? This way people could enjoy the benefits of your work without stable > > branch being disrupted and BC problems raised. > > > > -- > > Stanislav Malyshev, Software Architect > > SugarCRM: http://www.sugarcrm.com/ > > (408)454-6900 ext. 227 > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > >
