OSLib 6.11 Released

[Jonathan Coxhead]

   David ...

 | >    But in reality (with #include "oslib/os.h"), it will go looking for 
 | > OSLibInclude:oslib/os.h, which it will find as the same thing.
 | 
 | It does work, honest. [...]

   Sure it works, but it defeats the point. The reason to have the "oslib/" 
things everywhere is to avoid collisions with other names. People want to 
have the OSLib "os.h" *and* one from another library, at the same time. 
Clearly, the library headers have to include the disambiguated name, 'coz 
we don't want OSLib's "wimp.h" picking the "os.h" from a different library.

   Nice to hear you tried it, and it works, though.

        /|
 o o o (_|/
        /|
       (_/