MacArthur, Ian (SELEX GALILEO, UK) wrote: >>>> Fltk-1.1 : fltk-config, libfltk.a, etc. >>>> Fltk-2 : fltk2-config, libfltk2.a, etc. >>>> Fltk-utff8 : fltk-utf8-config, libfltk-utf8.a, etc. >>>> >>>> Where will fltk-1.3 fit in? >> I would stick with fltk-config for FLTK 1.x - the --version and >> --api-version options can be used to detect which 1.x version is >> installed. > > > OK, but at some point there's going to be some API breakage (e.g. the > overloading of position method in scroll or whatever) and that's going > to impact code compilation. I think I'd rather have a distinct version > of fltk-config that I could call, knowing which API it was "bringing > with it", rather than #ifdef'ing my code to use the appropriate API > based on version... Maybe... Something like that...
Yes, but the API breakage is a lot smaller than the move from 1.x to 2.0, which is why fltk-config is fltk-config2 in 2.0... As for #ifdef'ing code, a lot of applications already do this for 1.1.x changes, and several of the add-on widgets do it to be compatible with both 1.x and 2.x, so it isn't impossible... Configure checks can require a certain minimum version if you don't want to mess with #ifdef's. -- ______________________________________________________________________ Michael Sweet, Easy Software Products mike at easysw dot com _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
