1. Re: *nix configuration
Juergen Luethje wrote:
>
> I endorse this proposal!
>
> What I also would like is, making Euphoria better portable, so that it
> can be run smoothly e.g. from a USB drive. AFAIK the prerequisites for
> this are:
> a) Euphoria won't rely on any environment variables (and not on entries
> in the Windows registry, of course), but reads all settings from a
> configuration file instead. It could be a simple INI file, or even an
> XML file (which would allow to store anything and everything).
> b) The interpreters/translators would search for the configuration file
> firstly in their own directory (important if they are on a portable
> device). If no configuration file is found there, then they'll look
> for it in some standard places (such as %APPDATA% on Windows).
> c) No absolute path and file names are used, but only relative ones.
>
> Matt, can these ideas be arranged with your suggestion, or are there
> contradictions?
These are good inputs. I hadn't really thought too much about carrying
this effort over into a windows environment, but you made great points.
Please update the wiki:
http://rapideuphoria.wiki.sourceforge.net/nix+config
On *nix, my idea was to look in a standard place, such as
/etc/euphoria/euinc.conf
And euinc.conf would probably be a plain text file, with one path per
line that specified where to search for include files. On windows, it
could be stored in %APPDATA%\euphoria\euinc.conf.
But there should be a way to get a different conf file, which leads into
another idea regarding allowing interpreter specific command line switches
before the file name:
$ exu -c ./myinc.conf myapp.exu
> exw -i c:\wxeu wxeuapp.exw
command_line() would still work the same (so the interpreter would fiddle
with the actual command line passed in), and we might want to add an
additional routine like interpreter_options() to access those switches...
or maybe not.
Matt
