Run mode

[carlosalberto]

For purposes of the test626 integration, I'm considering a 'run' mode in ejs itself:

1. Compile to a temporary output, i.e. '/tmp/xasdadssdasd.out'
2. Simple invocation on that file.
3. Removal of that file.

This would look something like:

./ejs --run mysample.js [mysample args]

Simple, but I'm wondering if it's clean enough, and desirable - we may not want to let our users (for now) to do that directly.

(This is an alternative to creating a bash wrapper to do this for us, and then be passed to the test262 infrastructure).

[toshok]

would rather not conflate compilation + execution. Should be pretty trivial to write a driver script that does the ejs execution + test execution in a single step, right?

[carlosalberto]

Yes - either bash or in javascript itself. Lets keep it that way (for now).

Shall we close this issue then?

[toshok]

yeah let's close this then. I like the idea of it being js (a node script) simply because we assume node already. That means we should probably switch the existing tests over to using it (instead of a hacked together Makefile :)