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 ... > 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.
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. 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. -- Ian _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
