Suggestions

[Ainsley Pereira]

In message <200004211930.MAA20975 at purple.trimedia.sv.sc.philips.com>
          "Jonathan Coxhead" <jonathan at doves.demon.co.uk> wrote:

>  | Might I suggest putting "OSLibInclude:" in all the #includes in 
> oslib
>  | to prevent them clashing with user supplied headers?
> 
>    Just a question ... Originally, 
> 
>       OS$Path    was the path for header files, and
>       OSLib$Path was the path for the library itself
> 
>    (So you would compile with "cc -IOS: -LOSLib:".)
> 
>    At what point did OS$Path get changed into OSLibInclude$Path---
> which seems to be a much less convenient name? And why?

Not sure - I changed from #include "OS:" to "OSLibInclude:" when I
switched to 6.00, but I think I may have missed a version or two before
that.
Specifying paths on the command line doesn't disambiguate between your
own headers and OSLib's though. (I was trying to compile some code that
had a 'font.h' earlier, which meant that OSLib included that instead of
it's own font.h. My solution was to sed all oslib's includes to include
the path, and explicitly put the path in anything in my code that was
supposed to be OSLib's; hence the suggestion.)

~A.
-- 
 -----------------------------------------------------------
   / Ainsley Pereira       /   aka Marble on Snowplains   /
  /                       / telnet://snowplains.org:3456 /
 ------------------------------------------------------------