OSLib 6.11 Released

[David Bryan]

Jonathan Coxhead wrote:

>  | If what I have written above is wrong, then yes, I'm confused.
>  | 
>  | David Bryan
> 
>    Well, it could be me that's confused :-(
> 
>    Of course, the library *does* include header files, because each header 
> file can include others. I was only thinking about C files. Umm.
> 
>  | If I write the code
>  | 
>  |   #include "oslib/wimp.h"
>  | 
>  | then, within wimp.h, the compiler will come across
>  | 
>  |   #include "os.h"
> 
>    There's the fallacy---once the restructuring is done, "wimp.h" will 
> include the line
> 
>       #include "oslib/os.h"
> 
> or the whole thing is utterly useless.
> 
>  | It [would] go looking for oslib/os.h, which it'll find as
>  | 
>  |   OSLib:oslib.h.os
> 
>    No, it would go looking for OSLibInclude:os.h, which it would find as 
> $.OSLib.Core.oslib.h.os.

Really, it does go looking for OSLibInclude:oslib.h.os .  Well,
strictly speaking that's what cc goes looking for, gcc goes
looking for OSLibInclude:/oslib/os.h .

>    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.  I took OSLib 6.01.  Added in the extra
layer of oslib directories.  Added oslib/ to my source files.  And
it compiled no problem.  It was only after it all worked, that I
decided that, in fact, it shouldn't have.  I spent some time with
the -E flag, to convince myself it does.

-- 
David Bryan