JX9 Scripting Engine

An Embeddable Scripting Engine

Jx9 in 5 minutes or less

Here is what you do to start experimenting with the Jx9 scripting engine without having to do a lot of tedious reading and configuration:

download The Code

Get a copy of the last public release of Jx9 (A single 1.3 MB C file). Visit the download page for additional information.

Write Programs That Use Jx9

Below is a simple C program that demonstrates how to use the C/C++ interface to Jx9. This program compile and execute the following Jx9 scripts.

// Declare a JSON object and assign it to the variable $my_data
$my_data = {
     // Greeting message
     greeting : "Hello world!\n",
     // Dummy field
      __id : 1,
     // Host Operating System
     os_name: uname(), //Built-in OS function
     // Current date
     date : __DATE__,
     // Return the current time using an anonymous function
     time : function(){ return __TIME__; }
 };
// invoke JSON object members
print $my_data.greeting; //Hello world!
print "Host Operating System: ", $my_data.os_name, JX9_EOL;
print "Current date: ", $my_data.date, JX9_EOL;
print "Current time: ", $my_data.time(); // Anonymous function


That is, this simple Jx9 script when running should display a greeting message, the current system time and the host operating system. A typical output of this program would look like this:


Hello world!
Host Operating System:  Microsoft Windows 7 localhost 6.1 build 7600 x86
Current date: 2012-12-27
Current time: 10:36:02

Another Jx9 script that demonstrate how to use the built-in IO facility.


//Declare an empty JSON array
$num = [];

print "Enter a number (Decimal, Hex, Octal or Binary notation)\n";
//Populate the JSON array with the first entry
$num[] = (int)fgets(STDIN);

print "Another number\n";
$num[] = (int)fgets(STDIN);

print "Finally, one last number\n";
$num[] = (int)fgets(STDIN);

//show content
print "Before sorting\n";
print $num;

//Sort the array now
sort($num);
print "\nAfter sorting\n";
print $num;

This simple Jx9 script ask for three numbers (64 bit integers) from the standard input (STDIN), store the given numbers in a JSON array, perform a merge-sort using the built-in sort function and output the sorted array. A typical output of this program would look like this:


Enter a number
 50232
Another number
  80
Finally, one last number
  0xff
Before sorting
  [50232,80,255]
After sorting
  [80,255,50232]

 An implementation of the famous factorial function in Jx9.

print "Enter a number\n";

$num = (int)fgets(STDIN);


function factorial(int $num)

{

  if( $num == 0 || $num == 1 )

    return 1;

  else

     return $num * factorial($num – 1);

}

print "Facorial of $num = "..factorial($num);


One final Jx9 script that demonstrate how Jx9 can be used for processing external configuration file based on JSON using the built-in json_encode() and json_decode() functions.


// ---------------------- config_writer.jx9 ----------------------------

// Create a dummy configuration using a JSON object
$my_config =  {
  bind_ip : "127.0.0.1",
  config : "/etc/symisc/jx9.conf",
  dbpath : "/usr/local/unqlite",
  fork : true,
  logappend : true,
  logpath : "/var/log/jx9.log",
  quiet : true,
  port : 8080
 };

// Dump the JSON object
print $my_config;

// Write to disk
$file = "config.json.txt";
print "\n\n------------------\nWriting JSON object to disk file: '$file'\n";

// Create the file
$fp = fopen($file,'w+');
if( !$fp )
    exit("Cannot create $file");

// Write the JSON object
fwrite($fp,$my_config);

// Close the file
fclose($fp);

// All done
print "$file successfully created on: "..__DATE__..' '..__TIME__;

// ---------------------- config_reader.jx9 ----------------------------

// Read the configuration file defined above
$iSz = filesize($zFile); // Size of the whole file
$fp = fopen($zFile,'r'); // Read-only mode
if( !$fp ){
   exit("Cannot open '$zFile'");
}

// Read the raw content
$zBuf = fread($fp,$iSz);

// decode the JSON object now
$my_config = json_decode($zBuf);
if( !$my_config ){
    print "JSON decoding error\n";
}else{
  // Dump the JSON object
  foreach( $my_config as $key,$value ){
   print "$key ===> $value\n";
  }
}

// Close the file
fclose($fp);

The first script generate a JSON object holding some dummy configuration fields, create a disk file named config.json.txt using the built-in fopen() function and finally serialize the JSON object to disk using the fwrite() function. While the second script perform the reverse operation using the fread() and json_decode() functions.

As you can see, Jx9 is a powerful programming language with a friendly and familiar syntax with a rich standard library built with over 303 functions and 139 constants suitable for most purposes. Refer to the Jx9 Language Reference Manual for additional information.

Embedding Jx9 using the C/C++ API

Embedding Jx9 in a C/C++ host application is relatively easy. The three Jx9 scripts defined above can be embedded in an application with the same C/C++ interfaces. That is, this simple C program could be used to compile and execute all the Jx9 scripts defined above.



  1. /*

  2. * Compile this file together with the jx9 scripting engine source code to generate

  3. * the executable. For example:

  4. * gcc -W -Wall -O6 -o test jx9_intro.c jx9.c

  5. */


  7. /* Make sure you have the latest release of the JX9 engine

  8. * from:

  9. * http://jx9.symisc.net/downloads.html

  10. */

  11. #include <stdio.h>

  12. #include <stdlib.h>


  14. /* Make sure this header file is available.*/

  15. #include "jx9.h"


  17. /*

  18. * Display an error message and exit.

  19. */

  20. static void Fatal(const char *zMsg)

  21. {

  22.    puts(zMsg);

  23.    /* Shutdown the library */

  24.    jx9_lib_shutdown();

  25.    /* Exit immediately */

  26.    exit(0);

  27. }


  29. /*

  30. * VM output consumer callback.

  31. * Each time the virtual machine generates some outputs, the following

  32. * function gets called by the underlying virtual machine to consume

  33. * the generated output.

  34. * All this function does is redirecting the VM output to STDOUT.

  35. * This function is registered later via a call to jx9_vm_config()

  36. * with a configuration verb set to: JX9_VM_CONFIG_OUTPUT.

  37. */

  38. static int Output_Consumer(const void *pOutput, unsigned int nOutputLen, void *pUserData /* Unused */)

  39. {

  40.   /*

  41.    * Note that it's preferable to use the write() system call to display the output

  42.    * rather than using the libc printf() which everybody now is extremely slow.

  43.    */

  44.    printf("%.*s",

  45.        nOutputLen,

  46.       (const char *)pOutput /* Not null terminated */

  47.    );

  48.      /* All done, VM output was redirected to STDOUT */

  49.      return JX9_OK;

  50. }


  52. /*

  53. * Main program: Compile and execute the JX9 program defined above.

  54. */

  55. int main(void)

  56. {

  57.   jx9 *pEngine; /* JX9 engine handle*/

  58.   jx9_vm *pVm; /* Compiled JX9 program */

  59.   int rc;


  61.   /* Allocate a new jx9 engine instance */

  62.   rc = jx9_init(&pEngine);

  63.   if( rc != JX9_OK ){

  64.    /*

  65.     * If the supplied memory subsystem is so sick that we are unable

  66.     * to allocate a tiny chunk of memory, there is no much we can do here.

  67.     */

  68.     Fatal("Error while allocating a new JX9 engine instance");

  69.   }



  72.   /* Compile the test program defined above */

  73.   rc = jx9_compile(pEngine,JX9_PROG,-1,&pVm);

  74.   if( rc != JX9_OK ){

  75.     if( rc == JX9_COMPILE_ERR ){

  76.      const char *zErrLog;

  77.      int nLen;

  78.     /* Extract error log */

  79.     jx9_config(pEngine,

  80.         JX9_CONFIG_ERR_LOG,

  81.        &zErrLog,

  82.        &nLen

  83.    );

  84.    if( nLen > 0 ){

  85.       /* zErrLog is null terminated */

  86.       puts(zErrLog);

  87.     }

  88.   }

  89.   /* Exit */

  90.   Fatal("Compile error");

  91. }



  94. /*

  95. * Now we have our script compiled, it's time to configure our VM.

  96. * We will install the VM output consumer callback defined above

  97. * so that we can consume the VM output and redirect it to STDOUT.

  98. */

  99.   rc = jx9_vm_config(pVm,

  100.       JX9_VM_CONFIG_OUTPUT,

  101.       Output_Consumer, /* Output Consumer callback */

  102.       0 /* Callback private data */

  103.     );

  104.   if( rc != JX9_OK ){

  105.       Fatal("Error while installing the VM output consumer callback");

  106.    }



  109.   /*

  110.   * And finally, execute our program. Note that your output (STDOUT in our case)

  111.   * should display the result.

  112.   */

  113.   jx9_vm_exec(pVm, 0);



  116. /* All done, cleanup the mess left behind. */

  117.  jx9_vm_release(pVm);

  118.  jx9_release(pEngine);


  120.   return 0;

  121. }


We create a new Jx9 engine instance using a call to jx9_init() on line 62. This is often the first Jx9 API call that an application makes and is a prerequisite in order to compile Jx9 code using one of the compile interfaces.


We compile our Jx9 test program on line 73 using the jx9_compile interface.


We configure our Virtual Machine on line 99 by setting a VM output consumer callback named Output_Consumer(). All this callback does is redirecting the VM output to STDOUT using the libc printf() routine or the write() system call.


And finally we execute our Jx9 program on line 113 using a call to jx9_vm_exec(). Your standard output (STDOUT) should display the result.


Clean-up is done on line 117 and 118 respectively via calls to jx9_vm_release() and jx9_release().

Compile the program

Compile the target C file together with the jx9 engine source code to generate the executable. For example:

gcc -W -Wall -O6 -o jx9_test jx9_intro.c jx9.c

Working Examples

Sharing Data between the C Code and  Jx9 Scripts.

Sharing data between the host application and the target Jx9 script such as passing environments information, command line arguments or registering predefined variables such as your application name, copyright notice and so forth is relatively easy and is done via the foreign variable mechanism.

This simple Jx9 script output the content of some foreign variable decalred below.


print "Showing foreign variable contents\n";
//Scalar foreign variable named $my_app
print "\$my_app =" , $my_app..JX9_EOL;
//foreign JSON object named $my_data
print "\$my_data = " , $my_data;
//Dump command line arguments
if( count($argv) > 0 ){
 print "\nCommand line arguments:\n";
 print $argv;
}else{
  print "\nEmpty command line";
}
//Return a simple JSON object to the host application
$my_config = {
        "jx9_version" : __JX9__,  //JX9 Engine version
        "time" : __TIME__, //Current time
        "date" : __DATE__  //Current date
 };
 //terminate the script
 die;

The following C program demonstrate how data is shared between the host application and the running Jx9 script. The main() function defined below creates and install two foreign variables named respectively $my_app and $my_data. The first is a simple scalar value while the last is a complex JSON object. these foreign variables are made available to the running script using the jx9_vm_config() interface with a configuration verb set to JX9_VM_CONFIG_CREATE_VAR.


  1. /*

  2. * Compile this file together with the jx9 scripting engine source code to generate

  3. * the executable. For example:

  4. * gcc -W -Wall -O6 -o test jx9_hostapp_info.c jx9.c

  5. */


  7. /* Make sure you have the latest release of the JX9 engine

  8. * from:

  9. * http://jx9.symisc.net/downloads.html

  10. */

  11. #include <stdio.h>

  12. #include <stdlib.h>


  14. /* Make sure this header file is available.*/

  15. #include "jx9.h"


  17. /*

  18. * Display an error message and exit.

  19. */

  20. static void Fatal(const char *zMsg)

  21. {

  22.    puts(zMsg);

  23.    /* Shutdown the library */

  24.    jx9_lib_shutdown();

  25.    /* Exit immediately */

  26.    exit(0);

  27. }


  29. /*

  30. * VM output consumer callback.

  31. * Each time the virtual machine generates some outputs, the following

  32. * function gets called by the underlying virtual machine to consume

  33. * the generated output.

  34. * All this function does is redirecting the VM output to STDOUT.

  35. * This function is registered later via a call to jx9_vm_config()

  36. * with a configuration verb set to: JX9_VM_CONFIG_OUTPUT.

  37. */

  38. static int Output_Consumer(const void *pOutput, unsigned int nOutputLen, void *pUserData /* Unused */)

  39. {

  40.   /*

  41.    * Note that it's preferable to use the write() system call to display the output

  42.    * rather than using the libc printf() which everybody now is extremely slow.

  43.    */

  44.    printf("%.*s",

  45.        nOutputLen,

  46.       (const char *)pOutput /* Not null terminated */

  47.    );

  48.      /* All done, VM output was redirected to STDOUT */

  49.      return JX9_OK;

  50. }

  51. /*

  52. * The following walker callback is made available to the [jx9_array_walk()] interface

  53. * which is used to iterate over the JSON object extracted from the running script.

  54. * (See below for more information).

  55. */

  56. static int JsonObjectWalker(jx9_value *pKey,jx9_value *pData,void *pUserData /* Unused */)

  57. {

  58.   const char *zKey,*zData;

  59.   /* Extract the key and the data field */

  60.    zKey = jx9_value_to_string(pKey,0);

  61.    zData = jx9_value_to_string(pData,0);

  62.    /* Dump */

  63.    printf(

  64.      "%s ===> %s\n",

  65.      zKey,

  66.     zData

  67.   );

  68.   return JX9_OK;

  69. }

  70. /*

  71. * Main program: Compile and execute the JX9 program defined above.

  72. */

  73. int main(int argc,char **argv)

  74. {

  75.   jx9_value *pScalar,*pObject; /* Foreign JX9 variable to be installed later */

  76.   jx9 *pEngine; /* JX9 engine handle*/

  77.   jx9_vm *pVm; /* Compiled JX9 program */

  78.   int rc;

  79.   int n;


  81.   /* Allocate a new jx9 engine instance */

  82.   rc = jx9_init(&pEngine);

  83.   if( rc != JX9_OK ){

  84.    Fatal("Error while allocating a new JX9 engine instance");

  85.   }

  86.  

  87.   /* Compile the test program defined above */

  88.   rc = jx9_compile(pEngine,JX9_PROG,-1,&pVm);

  89.   if( rc != JX9_OK ){

  90.    if( rc == JX9_COMPILE_ERR ){

  91.      const char *zErrLog;

  92.      int nLen;

  93.      /* Extract error log */

  94.      jx9_config(pEngine,

  95.         JX9_CONFIG_ERR_LOG,

  96.         &zErrLog,

  97.         &nLen

  98.       );

  99.    if( nLen > 0 ){

  100.       /* zErrLog is null terminated */

  101.       puts(zErrLog);

  102.     }

  103.   }

  104.   /* Exit */

  105.    Fatal("Compile error");

  106.   }


  108. /* Register script agruments so we can access them later using the $argv[]

  109. * array from the compiled JX9 program.

  110. */

  111.  for( n = 1; n < argc ; ++n ){

  112.    jx9_vm_config(pVm, JX9_VM_CONFIG_ARGV_ENTRY, argv[n]/* Argument value */);

  113. }


  115. /*

  116. * Now we have our script compiled, it's time to configure our VM.

  117. * We will install the VM output consumer callback defined above

  118. * so that we can consume the VM output and redirect it to STDOUT.

  119. */

  120. rc = jx9_vm_config(pVm,

  121.       JX9_VM_CONFIG_OUTPUT,

  122.        Output_Consumer, /* Output Consumer callback */

  123.        0 /* Callback private data */

  124.     );

  125.    if( rc != JX9_OK ){

  126.        Fatal("Error while installing the VM output consumer callback");

  127.    }

  128.  /*

  129.   * Create a simple scalar variable.

  130.   */

  131.   pScalar = jx9_new_scalar(pVm);

  132.   if( pScalar == 0 ){

  133.      Fatal("Cannot create foreign variable $my_app");

  134.    }

  135.    /* Populate the variable with the desired information */

  136.    jx9_value_string(pScalar,"My Host Application/1.2.5",-1/*Compule length automatically*/); /* Dummy signature*/


  138.   /*

  139.    * Install the variable ($my_app).

  140.    */

  141.   rc = jx9_vm_config(

  142.          pVm,

  143.          JX9_VM_CONFIG_CREATE_VAR, /* Create variable command */

  144.          "my_app", /* Variable name (without the dollar sign) */

  145.           pScalar /* Value */

  146.        );

  147.     if( rc != JX9_OK ){

  148.        Fatal("Error while installing $my_app");

  149.     }

  150.   /* To access this foreign variable from the running script, simply invoke it

  151.    * as follows:

  152.    * print $my_app;

  153.    * or

  154.    * dump($my_app);

  155.    */


  157.  /*

  158.   * Now, it's time to create and install a more complex variable which is a JSON

  159.   * object named $my_data.

  160.   * The JSON Object looks like this:

  161.   * {

  162.   * "path" : "/usr/local/etc",

  163.   * "port" : 8082,

  164.   * "fork" : true

  165.   * };

  166.   */

  167.  

  168.   pObject = jx9_new_array(pVm); /* Unified interface for JSON Objects and Arrays */

  169.  /* Populate the object with the fields defined above. */

  170.   jx9_value_reset_string_cursor(pScalar);

  171.   /* Add the "path" : "/usr/local/etc" entry */

  172.   jx9_value_string(pScalar,"/usr/local/etc",-1);

  173.   jx9_array_add_strkey_elem(pObject,"path",pScalar); /* Will make it's own copy of pScalar */

  174.   /* Add the "port" : 8080 entry */

  175.   jx9_value_int(pScalar,8080);

  176.   jx9_array_add_strkey_elem(pObject,"port",pScalar); /* Will make it's own copy of pScalar */

  177.   /* Add the "fork": true entry */

  178.   jx9_value_bool(pScalar,1 /* TRUE */);

  179.   jx9_array_add_strkey_elem(pObject,"fork",pScalar); /* Will make it's own copy of pScalar */


  181.   /* Now, install the variable and associate the JSON object with it */

  182.   rc = jx9_vm_config(

  183.         pVm,

  184.         JX9_VM_CONFIG_CREATE_VAR, /* Create variable command */

  185.         "my_data", /* Variable name (without the dollar sign) */

  186.         pObject /*value */

  187.       );

  188.  if( rc != JX9_OK ){

  189.    Fatal("Error while installing $my_data");

  190.   }


  192.   /* Release the two values */

  193.   jx9_release_value(pVm,pScalar);

  194.   jx9_release_value(pVm,pObject);


  196.  /*

  197.   * And finally, execute our program. Note that your output (STDOUT in our case)

  198.   * should display the result.

  199.   */

  200.   jx9_vm_exec(pVm, 0);

  201.  /* Extract the content of the variable named $my_config defined in the

  202.   * running script which hold a simple JSON object.

  203.   */

  204.   pObject = jx9_vm_extract_variable(pVm,"my_config");

  205.  if( pObject && jx9_value_is_json_object(pObject) ){

  206.    /* Iterate over object entries */

  207.    printf("\n\nTotal entries in $my_config = %u\n",jx9_array_count(pObject));

  208.    jx9_array_walk(pObject,JsonObjectWalker,0);

  209. }

  210.  /* All done, cleanup the mess left behind.

  211.   */

  212.   jx9_vm_release(pVm);

  213.   jx9_release(pEngine);


  215. return 0;

  216. }

Get a copy of the C file.

Standalone Interpreter For Jx9

The Jx9 download page includes a simple standalone Jx9 interpreter named jx9 (or jx9.exe on windows) that allows the user to enter and execute Jx9 files against a Jx9 engine. This utility is available in prebuilt binaries forms or can be compiled from source. You can get a copy of the Jx9 interpreter from the download page.

To start the jx9 program, just type "jx9" followed by the name of the Jx9 file to xecute. That is, the first argument is to the interpreter, the rest are scripts arguments, press "Enter" and the Jx9 code will be executed.

If something goes wrong while processing the Jx9 script due to a compile-time error, your error output (STDOUT) should display the compile-time error messages.


Usage example of the jx9 interpreter:

Running the interpreter

jx9 scripts/hello_world.jx9.txt

Running the interpreter with script arguments

jx9 scripts/mp3_tag.jx9.txt /usr/local/path/to/my_mp3s


The Jx9 interpreter package includes over 40 Jx9 scripts to test from simple hello world programs to ZIP archive extracting, MP3 tag extracting, JSON encoding/decoding, INI processing, UTF-8 encoding/decoding and many more. These scripts are available in the scripts directory of the zip archive.

Next

Check out the Introduction To The Jx9 C/C++ Interface for an introductory overview and roadmap to the dozens of Jx9 interface functions.


A separate document, The Jx9 C/C++ Interface, provides detailed specifications for all of the various C/C++ APIs for Jx9. Once the reader understands the basic principles of operation for Jx9, that document should be used as a reference guide.


Any questions, check the Frequently Asked Questions page or visit the Support Page for online community support.


Symisc Systems
Copyright © Symisc Systems