Greg Ercolano wrote: > ... > I can't recall if FLTK initially used .C then later switched to .cxx > for its source, but for sure the .H convention stuck because app code > internal to DD was (I think?) already dependent on that casing.
Yes, when we started supporting Windows the .C extension was problematic since .C == .c in Windows-land. We opted to keep .H since it worked, although that has changed in 2.0... > But I agree, it rings 'ugly'. Changing it might be worse though, > because then the above cycle will probably happen again.. Agreed, although we could use the symlink trick for all of the .H files to phase out .H in favor of .h (or create .H files that included the .h files after issuing a compile-time warning...) Of course, the new "l33t" C++ header naming convention is to omit the extension entirely... -- ______________________________________________________________________ Michael Sweet, Easy Software Products mike at easysw dot com _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
