1. [E Digest - 24 to 25 Jul 1998 (#1998-69)] Maybe it's meant like
On Sun, 26 Jul 1998 00:00:21 -0400, Einar Mogen
<nord.staernes at ROLLAG.MAIL.TELIA.COM> wrote:
>....my main program includes a file like this:
>include others\foo.e
>then the file foo.e includes another file:
>include bar.e
>Both foo.e and bar.e lies in the directory others, but when bar.e is
>included, ex.exe looks in the main programs directory and
>c:\euphoria\include, and not in others\. Perhaps it is supposed to work =
like
>this, but I am tempted to call it a bug. The reason I just don't want to
>change the include in foo.e to:
[et ceterated]
I've noted this before, and proposed to Rob that Euphoria behave
as a number of other compilers/interpreters do - an environment
variable (EUDIR? EUINCLUDE?) contains a semicolon-separated list
of directories; on processing an include, the interpreter looks
in each of those directories until it finds a match. This could
be problematical if there are two files that have the same name
but in different directories, but there's no way to protect
against everything - and it wouldn't stop the user from putting
in a longer path - e.g., "include foo\bar.e" would look for a
file "bar.e" in a subdirectory "foo" of each path in EUINCLUDE.
The only time that the search is overridden is if the include is
given in a root-relative or drive-relative form (e.g., "include
"\foo\bar.e" or "include c:foo.e" or "include
f:\quux\wossname.e")
I really think that this is a "must have" for Euphoria to be
usable as a serious language for development - especially in a
multi-programmer environment.
--
Jeff Zeitlin
jeff.zeitlin at mail.execnet.com
