OSLib 6.11 Released

[Jonathan Coxhead]

   On 28 Sep 00, Chris Rutter wrote,

 | On Wed, 27 Sep 2000, Jonathan Coxhead wrote:
 | 
 | >    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.
 | 
 | Yik, but!  This makes assumptions about how the user has his include
 | paths setup, and specifically that #include "oslib/FOO" will `work';
 | the user may have added OSLib only to his system include path, for
 | instance.

   Yep, that's the sine qua non. The system you describe would just be 
broken. (OSLib is not a part of the system---it's a 3rd party library.)

 | Surely wimp.h should contain the line:
 | 
 |     #include "../../computer/oslib/os.n"
 | 
 | which is admittedly cumbersome to look at, but that's unimportant when
 | the header file are generated by tool.

   No ... double yik to that!! (At least!)

   The "approved form" should become

      #include "oslib/os.h"

and that's what the library should use. This lets anyone use any header 
file in any environment, subject only to the restriction that none of their 
headers lives in a directory called "oslib". That seems like the least that 
we can ask, and that's all we do ask. We can also easily provide legacy 
help for those want to continue using

      #include "os.h"

so why not?

   Assuming Tony likes any of this, of course :-)

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