1. Include files/project structure/which file to run?
If you have eg main.exw which has:
include get.e --(because it [main.exw] uses it)
include save.e -- also has include get.e(ditto)
include open.e -- also has include get.e(ditto)
Which is all good & proper. Also, save.e can validly have "include
main.exw" - clearly the interpreter ignores any already processed
include files. Good; smart; agreed, I understand why that's needed &
it works well.
Question: could there be a simple & minor change to the include
directive that lets me know that in save.e the "include main.exw" is
"dummy";, the interpreter will effectively ignore it, but reading the
source I now know what routine this is actually part of/in the editor
the run command checks & runs main.exw instead of save.e.
The other (possibly better) option is to mod the linux jobbie (from
the Eu reference manual):
"On the first line (only) of your program, you can use a special
comment beginning with #!, e.g.
#!/home/rob/euphoria/bin/exu
This informs the Linux shell that your file should be executed by the
Euphoria interpreter, and gives the full path to the interpreter. If
you make your file executable, you can run it, just by typing its
name, and without the need to type "exu". On DOS and Windows this line
is treated as a comment. "
(I know some bash, but little/no sh/ksh/csh et al to know what could
be got away with on the end of that line - obviously the shell, not
euphoria is interpreting it; euphoria treats it as a comment in all
cases.)
Pete
