[long discussion: we need some word(s) that would allow people
to portably specify that some source file to be INCLUDED
comes from a library, or that its path is relative to the path
of the current file]
On Apr 12, 7:34 am, Bruce McFarling <agil...@[EMAIL PROTECTED]
> wrote:
> On Apr 11, 2:19 pm, m_l_g3 <m_l...@[EMAIL PROTECTED]
> wrote:
>
> > INFORMATIVE we must allow the no-op implementation like
> > : ANCHORED ;
>
> Why?
>
> If it does not translate from a relative file reference to an absolute
> file reference, it is better that it not exist in the dictionary than
> that it exists but does not perform the semantics of ANCHORED.
Why do you require that the paths returned from [LIB-]ANCHODED
are namely *absolute*?
IMO, it is enough to know that the file will be found in the right
directory.
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).
By the way, "%SRCDIR%/aux/foo.fth" is not really absolute.
> ANCHORED ( ca1 u1 -- ca2 u2 )
> Translate the relative file reference in the string referred by
> ( ca1 u2 )
> into an absolute file reference.
> If executed from within a file script, the reference is relative to
> the location of that file script within the file system. If executed
> from the command line, the reference is relative to an implementation-
> defined location in the file system.
> The relative file reference consists of a file name and optional
> subdirectory prefix. Any subdirectory name in the subdirectory prefix
> concludes with the the subdirectory separator ``/''. The format of the
> absolute file reference is the implementation-defined format for use
> with the standard word INCLUDED.
> The absolute file reference returned by ANCHORED may be over-written
> by the next invocation of ANCHORED or LIB-ANCHORED.
My understanding of this text is:
relative = relative to the path of the current file
absolute = not relative to the path of the current file, but whatever
the system imlementor likes.
The text
> The format of the
> absolute file reference is the implementation-defined format for use
> with the standard word INCLUDED.
indicates that it the "absolute" file reference format is defined not
even by OS, but by the Forth system.
Therefore, "absolute" may in fact be relative to a location
chosen by the implementor, for example, relative to
the installation diretory.
In addition, INCLUDE may already have some built-in logic. For
example, it may consider all file references as relative to the
location of the current file. (IOW, INCLUDE already does what ANCHORED
is for). IMO, in this case it is acceptable to allow a no-op ANCHORED.
> it is better that it not exist in the dictionary than
> that it exists but does not perform the semantics of ANCHORED.
The mentioned semantics is built into INCLUDED.
ANCHORED may be a no-op.
(yes, loading from the current directory will be a problem... at
least, without WRK-ANCHORED)
|
