> Regarding the question of providing a migration path, IMO it's > oftentimes easier to keep a deprecated class around for awhile, > as opposed to some methods. Here that means renaming the > existing Fl_Input to Fl_Input_Deprecated (or something) while > making the proposed changes to Fl_Input. I think that makes > it easier for affected developers to migrate, because the > change is more centralized. I haven't got any hard evidence > to support this claim of course, it's just sort of a gut feeling.
-1 on this proposal. Everyone's code would break, and they would be forced to either rename all use of Fl_Input to Fl_Input_Deprecated, or update the method calls to the new interface. D. _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
