ServerJS/C API: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 7: Line 7:
* The JSAPI is the C API for the [https://developer.mozilla.org/en/SpiderMonkey SpiderMonkey] JavaScript engine https://developer.mozilla.org/En/SpiderMonkey/JSAPI_
* The JSAPI is the C API for the [https://developer.mozilla.org/en/SpiderMonkey SpiderMonkey] JavaScript engine https://developer.mozilla.org/En/SpiderMonkey/JSAPI_
* NSPR API Reference https://developer.mozilla.org/en/NSPR_API_Reference
* NSPR API Reference https://developer.mozilla.org/en/NSPR_API_Reference
* Ejscript http://www.ejscript.org/products/ejs/doc/api/native.html is a complete native API to create objects, classes and composite native types. It also supports loadable modules with backing native libraries.
* jsffi http://code.google.com/p/jslibs/wiki/jsffi is a module that allow you to call any symbol in a native module (dll/so).
* jsffi http://code.google.com/p/jslibs/wiki/jsffi is a module that allow you to call any symbol in a native module (dll/so).
* jsext "Including C functions" http://jsext.sourceforge.net/Including%20C%20functions.html
* jsext "Including C functions" http://jsext.sourceforge.net/Including%20C%20functions.html

Revision as of 05:22, 12 February 2009

C API

For C/C++ based JavaScript interpreters, being able to interface easily with C libraries is a big win because of all of the available functionality. Each JavaScript interpreter has its own bridge to C, but if there is some common API (possibly exposed at the JavaScript level as in ctypes), then this will make it much easier to share work between interpreters.

Prior Art