DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New] Link: http://www.fltk.org/str.php?L2513 Version: 1.3-current One question though -- I looked at the commit. Shouldn't the #include for AvailabilityMacros.h be /above/ our #ifndef/#define/#endif for the version #s? I'm thinking that since that's the include file that sets these values, it'd be best to #include Apple's values first, then set any macros they didn't set. Currently it reads: ---- [..] #ifndef MAC_OS_X_VERSION_10_5 #define MAC_OS_X_VERSION_10_5 1050 #endif [..] #include <AvailabilityMacros.h> ---- I'm guessing if Mac comes out with a 10.10.0 release, they'll probably change all the numbers around (eg. 1050 would change to 10050 so that they can have a 10100). So we'd want to have the newer release's definitions so that the comparisons to MAX_ALLOWED still work. I'd think we'd only want our defines to 'fill in the gap' when being built on older systems that don't set them. FWIW, in my setup I tried moving the #include <AvailabilityMacros.h> above our defines, and that seemed to work too on my systems. But maybe I'm missing something. Link: http://www.fltk.org/str.php?L2513 Version: 1.3-current _______________________________________________ fltk-bugs mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-bugs
