Re: include paths

new topic     » goto parent     » topic index » view thread      » older message » newer message

On 15 Jan 2001, at 2:09, George Henry wrote:

> Hi all, esp. Rob.
>
> I think the interpreter should include in its search path for include files
> the current directory (or folder) of the file currently being read, plus it
> should use some sort of path statement to find include files in a wide variety
> of directories.
>
> I just switched to win32lib version 0.55, which includes files
> tk_something.e, one or more of which in turn include w32keys.e. Now, all of
> these files are together in their own directory, where I wish to keep them.
> But no, either I have to change the source to include explicit paths, or move
> them into either the \euphoria\include directory or my main project directory.
> This is an irritant.
>
> In contrast, most C compilers (and I suspect, other languages as well) allow
> you to list the all folders where include files might be found, and search all
> the specified folders. Limiting includes to 1. the \euphoria\include
> directory; 2. the user's project directory; and 3. paths given explicitly in
> the source seems unreasonably hampering.

How about the

C:\Eu_project_1\include
D:\Eu_project_2\include

directories?

Kat

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu