> Perhaps we could also allow defining FL_UNSTABLE or > FL_UNPORTABLE to get the OS-specific definitions then?
Oh yes, I can see that working, +1, Some sort of FL_<low_level_feature_here_be_dragons...> option sounds like a good idea, and we separate the Fl_X stuff from the FL_LIBRARY option, resolving Albrecht's point. Though if we are doing that, I guess we'd need to do it before 1.3.0 goes final. SELEX Galileo Ltd 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-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
