imacarthur wrote: > On 21 Sep 2008, at 17:34, Fabien Costantini wrote: > >>> This very delicate aspect as to be more discussed, for the record >>> currently we can read in the sources: >> // the following methods (maxinum and mininum) are kept for >> compatibility >> // we must keep binary compatibility ...
I would vote for dumping these. We can easily announce that they are gone in the CHANGES file. They are already in 1.1 deprecated and could be replaced by the correctly written methods (even in 1.1). >> Binary compatibility is a very high restricting statement, do we need >> that anymore in 1.3 ? >> I guess not but would like to have some acknowledge about these. Not between (minor) version changes, IMHO, but _within_ 1.3 we should have binary compatibility. > For what it's worth, binary compatibility (with the 1.1.x tree) is > broken already by changes in 1.3. > The API is still compatible, but the ABI is not. There are also changes in the API (e.g. Fl_Scroll::scroll_to(x,y) instead of Fl_Scroll::position(x,y)). I could see that one of my app's features failed when tested with 1.3 (that _was_ expected), although it compiled without error messages. I can also see that changing the widget coordinates from short to int _could_ affect some programs, and there may be more. > So, for my money, if there are ABI breaking enhancements to be made, > they should be made now, whilst there is no 1.3 based code out in the > wild that will be broken by these changes. Seconded. I'm working on a change that Fl_Scroll would not have its scrollbars as children in its Fl_Group - IMO a _valuable_ change. But OTOH this could affect user code, where someone relies an these two additional children of the group. BTW: There's a working version that you can check out at: <http://svn.easysw.com/public/fltk/fltk/branches/branch-1.3-composite> Please read the CHANGES.branch file for more info. Feedback would be welcome. The current version has some printf debug statements active, I'll fix that soon. Albrecht _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
