Re: EuDir and EuInc
Chris Bensler wrote:
>
> Matt Lewis wrote:
> >
> > Jeremy is correct. They're not being removed, but they won't be required.
> > As the link says, there will be specified places where the euinc.conf files
> > can be located. You could read those to search for the installed win32lib.
>
> PLEASE don't disperse my Euphoria environment! I like the fact that I could
> just copy my euphoria folder to wherever I want.
>
> Use EUDIR to locate the config file in the eu/bin folderer.
> If EUDIR is not defined, base off of the location where the interpetter is
> executed from.
>
> Just please don't start spreading out the environment to obscure locations.
What platform do you use?
In any case, the 'default' layout will probably stay the same. If you install
using a package manager on *nix, however, euphoria will obey the file structure
layout of your distro, which makes a lot of sense for those platforms.
The goal is to make Euphoria a first class citizen, and hopefully to get it
into the standard repositories. These dispersed locations are actually the
opposite of obscure on those platforms. We'll also have things like man
pages. I think this step will allow growth for the language.
As I said, windows will probably stay basically the same, but you *will* be
able to use the logical places to put euinc.conf files. You can keep them
right in the same folder as the interpreter. Or you can store them in the
windows acceptable places (i.e., Documents and Settings\user\Application Data).
Or you can continue to use EUDIR and EUINC, which will still be there, and
they get the job done. Where they become difficult is if you're developing
either euphoria itself, or working with multiple versions of a lib. Using
the conf files (or simply passing include directories on the command line)
really shine then.
Matt
|
Not Categorized, Please Help
|
|
