I see what you mean, Norris: it would get a little haywire to have to track which file (if any) were being evaluated at any given moment, particularly if code in one file were calling functions in another, and back and forth. I guess my question was probably naive, but thanks for your reply.
I solved my problem in a more natural way, I think. I've written my own wrapper application which takes a single filename as one of several arguments, it then passes that filename on to Rhino to run as one of _its_ arguments. At first this approach seemed a little inside- out, but actually it gives me finer control over how my application is called and treats Rhino more like an embedded engine, which works perfectly! Thanks again, Michael On Jan 15, 4:05 pm, Norris Boyd <[EMAIL PROTECTED]> wrote: > Here's what I was thinking when I wrote the arguments array in the > shell: The idea is that these are the arguments to the script, thus > arguments[0] is the first argument to the script. Note that the -f > option to the shell permits multiple script filenames to be executed > on a single shell session, so just looking at the first argument to > the shell wouldn't be sufficient anyway. _______________________________________________ dev-tech-js-engine-rhino mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-js-engine-rhino
