Re: [RFC] Turn gc_collect_cycles into a function pointer

On Fri, Dec 5, 2014 at 2:01 AM, Benjamin Eberlei <kontakt@beberlei.de> wrote: > > I agree, this change makes sense this way and is compatible to the way > hooks work right now. This change can be part of the grand refactoring > later on. 7.0 is indeed the best time to do it. > Refactoring the whole extension API is a bit time critical anyways, if we > won't find a champion for this in the next days/weeks then it won't happen > for 7.0 and then by definition (BC breaks) not for any version in 7.* > branch. This is not correct. The BC break clause applies only for userland. While we try to avoid big APIs change between x.y and x.y+1, we do allow them. However I worry much more about what we do (not) for userland and some bigger changes internally, those that will be very hard to sell for 7.x. > Expanding the scope of this too much will end up as failure. -- Pierre @pierrejoye | http://www.libgd.org