OSLib 6.11 Released

[David Bryan]

Jonathan Coxhead wrote:

>    On 28 Sep 00,, David Bryan wrote,
> 
>  | You don't even need to use "oslib/os.h" within the library, "os.h" will
>  | do.
> 
>    Nope!
> 
>    *If* the library was written in C (which it isn't),

But, it's compiled from machine generated assembler, which doesn't
even need the existence of the C header files.

> and *if* the sources 
> were in the same place as the headers (which is a bit moot ...)

But, it's compiled from machine generated assembler, which doesn't
even need the existence of the C header files.

> and *if* it 
> was kept in one flat directory (which it won't be), you could do that.

If I write the code

  #include "oslib/wimp.h"

then, within wimp.h, the compiler will come across

  #include "os.h"

It'll go looking for oslib/os.h, which it'll find as

  OSLib:oslib.h.os
 
>    So I think you're a little confused! :-)

If what I have written above is wrong, then yes, I'm confused.

-- 
David Bryan