> >> 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... SELEX Sensors and Airborne Systems Limited Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3EL A company registered in England & Wales. Company no. 02426132 ******************************************************************** This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ******************************************************************** _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
