As far as I recall, the Directories proposal foundered on the question
of what should be the prefix. If "name.fs" is in the current working
directory, and in "./name.fs", "./" is conventionally a no-op, then
how can "./" change the meaning from cwd to the current source
directory?
How about: no prefix?
SF" ..." returns a string anchored in the directory of the source file
(or an implementation specified home/default directory if executed
from the command line).
WF" ..." returns a string that refers to a file anchored in the
current working directory.
LF" ..." returns a string that refers to a file anchored in the
current library directory.
So ...
LF" nicl/panel.nlf" REQUIRED
.... would return whatever string is needed to refer to the file
``panel.nlf'' in the subdirectory ``nicl'' in the library directory.
.... and if ``panel.nlf'' had the string
[optional] {gforth} [IF] SF" gforth/panel.fsn" INCLUDED [THEN]
.... that would refer to the subdirectory ``gforth'' in ``nicl''.
