OSLib 6.11 Released

[Jonathan Coxhead]

On 26 Sep 00,, Chris Rutter wrote,

 | On Tue, 26 Sep 2000, Tony van der Hoff wrote:
 | 
 | > In any case, Why do you think this is an improvement on
 | > "section/header.h" which Jonathan proposed?
 | 
 | Oh -- I thought it was relative to the current file, personally.  It
 | certainly seems to be in the build setups I have here.

   #include is relative to the file that contains the line (in ANSI C). The 
K&R rule was different, but not often seen now.

 | Um, because that approach requires that the OSLib root be in your
 | path -- you may not /want/ OSLib in your path -- I certainly don't;
 | I include "oslibinclude:foo.h", and don't want its namespace intruding
 | upon mine in any other circumstance.

   This is the problem with multiple -I options: it mashes all the contents 
of all the directories into 1 big lump, and makes it hard to control 
multiple files with the same name.

   I think this is another vote for putting a "/" in the #include directive
---would you be happy writing

      #include "oslib/foo.h"

and compiling with -IOSLib:?

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