-
Notifications
You must be signed in to change notification settings - Fork 35
Console Runner
There is a console runner available from ReoScript v1.2. The script file could be executed by this shell runner program.
Download ReoScript binary library or build source file. Console runner could be find in the following path:
ReoScript\ReoScriptRunner\Bin\Debug
If you build ReoScript with Release configuration. The last folder should be 'Release'.
-
Open Notepad, write following code and save as file named "Sample.rs":
function hello() { console.log('Hello World!'); } hello();
-
In command prompt, execute following command:
C:\> ReoScript.exe Sample.rs
-
The 'Hello World!' will be printed out:
C:\> ReoScript.exe Sample.rs Hello World! C:\>
All Core Features will be supported if script executed from Console Runner. See more about CoreFeatures.
-
-workpath: Specify the work path for Runner
When another script file may be imported from current script file by import keyword. The relative path of script file depends on workpath to locate where does the file exist. e.g.:
Sample.rs:
import "other.rs"; // import another script file other_func(); // dummy call function defined in other.rs
By default, ReoScript uses the path where ReoScript.exe was started up as default workpath. If the workpath is C:\, ReoScript will also find other.rs in C:\. However, you could explicitly change the workpath to another path as below:
C:\> ReoScript.exe Sample.rs -workpath "D:\Scripts"
-
-debug: Enable debug support
There is a object name 'debug' will be added into SRM. The debug object provides the following methods:
- debug.assert(boolean)
- debug.assert(result, expect)
- debug.Stopwatch
For example:
C:\> ReoScript.exe Sample.rs -debug
-
-exec: Run specified script
Sample.rs:
function hello() { console.log('Hello World!'); }
Execute runner with -exec argument:
C:\> ReoScript.exe Sample.rs -exec "hello();" Hello World! C:\>