On 11.09.2009, at 21:24, Greg Ercolano wrote: > Too bad there isn't some way the new #include files could detect > if there's a mix of the old ones. I don't think the FLTK version > macros can really help us here, since those only get set once. > But if they were set and reset each time they were include'ed, > we could detect them, and throw a #warning. > > Tough problem..
There should be a way to solve this with a smart order of undefs and ifdefs. It would be worth the effort IMHO. Out of the blue, I think something like this may work: #undef FLTK_1_3 #include <FL/Fl_Window.H> #ifndef FLTK_1_3 # warning "Version trouble!" #endif and in Fl_Window.H, we would #define FLTK_1_3 for later versions, we need to search and replace FLTK_1_3 with FLTK_1_3_1, etc. It should also be possible to verify that the included files match a statically linked library - at least at run-time. _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
