On Apr 14, 11:35 am, m_l_g3 <m_l...@[EMAIL PROTECTED]
> wrote:
> Why do you require that the paths returned from [LIB-]ANCHODED
> are namely *absolute*?
Probably as a shorthand for what I mean ... standardese is not my
first language.
I mean that it is an unambiguous file reference to a specific file in
a specific file location, as understood by INCLUDED.
> IMO, it is enough to know that the file will be found in the right
> directory.
Yes, but the purpose of ANCHORED and LIB-ANCHORED is that the input
string refers to a file in a portable manner, and the output refers to
the file in the way that the implementation INCLUDED (etc.) can use
it.
> Anyway, a portable program will have no way to distunguish between
> absolute and relative (because it will not know under which OS, if
> any, it is running).
Yes, that's why it needs the implementation to export words to it that
translate from the portable file reference to the file reference used
in the system.
IOW, that's the reason for wanting the words ANCHORED and LIB-
ANCHORED ... because otherwise its not something that the portable
code can do for itself without a larger set of support words.
Imposing a single standard system for referring to a specific file in
a specific location for all Forth systems in all operating systems is
an impossible goal. Reserving a couple of word names for process of
translating from a portable format to the local format is not an
impossible goal.
|
