Suggestions

[David J. Ruck]

On Thu 04 May, David Bryan wrote:
> In message <$YUGeIABvaE5Ew6j at mk-net.demon.co.uk>
> As the path defined by OSLib$Path was not a component of OS$Path,
> this would have meant having five components in one path variable. 
> This would reduce the depth in the directory hierarchy you could
> place the library without hitting the 255 character limit on
> environment variables earlier versions of RISC OS have.
> 
> 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.

I'd like to see all the header files in one directory (c and asm seperate
ofcourse), it certainly makes looking for things much easier, as the location
of some header files are is immediate obvious. But it would restrict pre-E+
format users to keeping in a 3rd party file system such as RaFS which
wouldn't be acceptible. Maybe an obey file to flatten the structure and alter
SetVars could be included?

Cheers
---Dave