[..] > > That said, I agree that we should change the API, but I would like > to keep the old function as a compatibility wrapper for a while, > as Greg also suggested. > > IMHO we should add a new method, document that the old method > is deprecated, and remove it in the following release after 1.3.x, > i.e. 1.4 or 3.0. > [..] > More comments/proposals? > > Albrecht
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. Best, Stan _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
