OSLib 6.11 Released

[Chris Rutter]

On Thu, 28 Sep 2000, David Bryan wrote:

> Excellent Chris?  You don't even need to use "oslib/os.h" within
> the library, "os.h" will do.

The library should always, /always/ use relative paths, in my opinion.
This is impervious to failure due to the user's include path configuration.
If it does, the library's own #includes needn't be worried about, whatever
the case.

c.