imacarthur wrote: > > On 4 Nov 2008, at 18:09, Maik Beckmann wrote: > >> The >> Fl -> FL >> *.h -> *.H >> stuff looks pretty scary to me. I've never encountered such stuff >> before. >> Why do we do it? > > History. Backwards compatibility. > In particular, it often allows (badly written) code ported from win32 > or OSX systems onto *nix systems to compile without choking, as many > programmers on those systems are so used to having a case-insensitive > file system that they are "haphazard" with the case of their include > paths...
So, which one should be used: The symbolic link (Fl/*.h) or the hard link (FL/*.H)? I have been using: #include <FL/Fl_Button.H> Now I am wondering if I should be using the symbolic links instead? -- Alvin _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
