> When we do the merge, and we find differences between the nominally > similar F1 and F2 implementations, how do we choose between them? Taking a function: if the semantics of fltk1 and fltk2 implementations are exactly the same, of course we choose code of F1, but looking at the diff between them. If not, we sit and think. That depends on the concrete case. > Also, how do we decide exactly what the F2 API is, as it still seems to > change...? Still, with this approach, maybe that doesn't matter so > much... I think we just don't need to decide that :) If you mean the core interface after merge - while taking stable code, we can change the interface all the time. I mean, if, say, we have merged out some class, and then notice that its API could be made better - we change it.
_______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
