ServerJS/C API: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(New page: = 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 ...)
 
Line 8: Line 8:
* NSPR API Reference https://developer.mozilla.org/en/NSPR_API_Reference
* NSPR API Reference https://developer.mozilla.org/en/NSPR_API_Reference
* 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
* js-ctypes https://wiki.mozilla.org/JSctypes is a foreign-function library for Mozilla’s privileged JavaScript. It provides C-compatible data types and allows JS code to call functions in shared libraries (dll, so, dylib) and implement callback functions.
* js-ctypes https://wiki.mozilla.org/JSctypes is a foreign-function library for Mozilla’s privileged JavaScript. It provides C-compatible data types and allows JS code to call functions in shared libraries (dll, so, dylib) and implement callback functions.
* SpiderApe plugins http://spiderape.sourceforge.net/plugins/
* SpiderApe plugins http://spiderape.sourceforge.net/plugins/
* NSPR API Reference https://developer.mozilla.org/en/NSPR_API_Reference
* NSPR API Reference https://developer.mozilla.org/en/NSPR_API_Reference

Revision as of 08:59, 5 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