OSLib 6.11 Released

[Jonathan Coxhead]

   On 28 Sep 00, David Bryan wrote,

 | The compiler treats the filename for wimp.h as 
 | 
 |  OSLibInclude:oslib.h.wimp
 | 
 | When it encounters
 | 
 |   #include "os.h"
 | 
 | it strips off the "h.wimp", and adds "h.os".  So it will be
 | looking for
 | 
 |  OSLibInclude:oslib.h.os
 | 
 | Which it unambiguously finds :-)

   But it finds "oslib/wimp.h" in "<OSLib$Dir>.User.oslib.h.wimp, so won't 
it look for "os.h" in there? And fail to find it, and then scan the rest of 
the -I options (and find it at that point)?

 | The only reason I even suggested this was: If you have
 | "oslib/os.h" in the library header files, and the user wants to
 | carry on using "wimp.h", the search path has got to have all the
 | directories both with and without the final "oslib".  This is only
 | likely to cause more emails to Tony.  "I've put all six
 | directories on the search path, and it doesn't work."  The answer
 | being, "Well, you now need twelve."

   That seems like a pretty manageable change, to me, and well in keeping 
with other relevant standards and practices, etc.