Suggestions

Tony van der Hoff OSLib at mk-net.demon.co.uk
Fri May 5 10:00:41 BST 2000


On Thu, 4 May 2000, at 18:22:26, David Bryan <D.J.Bryan at cranfield.ac.uk>
wrote on the subject "Suggestions":

>
>It would seem to be a bit academic now.  OSLibInclude$Path now
>consists of 6 components, and for me, eval LEN"<OSLibInclude$Path>"
>gives 303.  Just using OSLib$Path now seems very sensible :-)
>
>You could, of course, move o.OSLib to, say, Core.o.OSLib.  But
>then that would be misleading.
>
Indeed, that would be IMO unacceptably misleading, and not very logical.
However, maybe moving types.h and macros.h into Core would be possible,
although that fails on the logical criterion.

Before you ask, Jonathan, the move of types.h to types.h.types and
macros.h to macros.h.macros was to support those users who expected to
see a 'standard' directory structure (c.s.a.p thread about a year ago).
-- 
Tony van der Hoff         |  Mailto:tony at mk-net.demon.co.uk
                          |  Mailto:avanderhoff at iee.org
Buckinghamshire, England  |  http:www.mk-net.demon.co.uk



More information about the oslib-user mailing list