Hello !
> I imagine that you wouldn't want to change anything in 1.1.x and > 1.3.x, because you don't want to break programs that #include the .H > or .h files on case-sensitive systems. But for FLTK 2.x? I'd say > there's a strong case for just going with ".h". Even with 1.3 people should be forced to either use this or that way. Even if a source file uses the wrong way, it is not hard to change it. Searching for a string and changing it can be automated with commandline tools. CU _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
