Albrecht Schlosser wrote: > ... > (3) maybe also remove old compatibility functions and methods from the > sources (but who would know, which we can remove?). Call them > "deprecated" in a first step (1.3), and remove them later (1.4/1.5/1.6)?
+1 I'd deprecate the functions and non-UI classes in 1.3 (and there are GCC attributes that can be used for this, just make sure that the build of FLTK itself doesn't generate the warnings, please :) and add a note that we no longer test (did we ever?) for forms compatibility. In 1.4 we can remove the forms functions and non-UI classes. -- ______________________________________________________________________ Michael Sweet, Easy Software Products mike at easysw dot com _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
