I don't remember of any change in other binding (not saying there were not any) which like this one were removing a feature without giving an alternative to do the same thing. If someone can point me to one, I'll be glad to look at how we managed this.
Pierrick On 20 December 2012 11:57, jpauli <jpa...@php.net> wrote: > > > On Thu, Dec 20, 2012 at 4:57 PM, Pierrick Charron <pierr...@webstart.fr> > wrote: >> >> Hi Julien, >> >> I think we need to trigger a notice to prevent users to write code >> that may not work in future version even if it doesn't depend on our >> changes but on libraries changes. >> >> Maybe we could be more explicit and tell the user that the 1 value >> will not be available as of libcurl 7.28.1 (I just hope that people >> will not be confused on what is libcurl and what's the version of it). > > > Well, I'd say what have we done before about that ? > We have already met lib API changes (libcurl, libxml, other usefull libs > exposed to the user), let's see what we did :-) > > Julien.P -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
