David Megginson wrote:
> Erik Hofman writes:
> 
>  > -rw-r--r--    1 erik     user       648823 May 12  2001 js-1.4-2.tar.gz
>  > -rw-r--r--    1 erik     user      1046117 Mar 13 19:12 js-1.5-rc4.tar.gz
> 
> What does everyone else think?  Should this be bundled unpacked in the
> SimGear source tree and built automatically (as with expat, our XML
> parser), bundled as an archive so that users can build it if they
> don't already have it installed (as with metakit and zlib), or left as
> an external, optional extra?  I'd like to embed an interpreter in
> FlightGear, and ECMAScript is an excellent candidate language, but it
> would be nice if the interpreter were a lot smaller.
> 
> Erik -- what do your bindings look like?

You mean the code to bind a JavaScript function to a C function:

static JSBool
_fgs_set(JSContext *cx, JSObject *obj, uintN argc, jsval *argv, jsval *rval)
{
    const char *node, *str;

    if (argc != 2)
       return JS_FALSE;

    if ((node = JS_GetStringBytes(JS_ValueToString(cx, argv[0]))) == NULL)
       return JS_FALSE;

    if ((str = JS_GetStringBytes(JS_ValueToString(cx, argv[1]))) == NULL)
       return JS_FALSE;

    _fgs_root_node->setStringValue(node, str);
    *rval = BOOLEAN_TO_JSVAL( true );

    return JS_TRUE;
}


or do you mean:

fgfs.set
fgfs.setBoolean
fgfs.get
fgfs.getBoolean

etc.

Erik


_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel

Reply via email to