Subj : Re: (Spidermonkey) Converting a property name to a tinyId
To   : netscape.public.mozilla.jseng
From : zakalawe@mac.com (James Turner)
Date : Tue Mar 18 2003 02:22 pm

Brendan Eich <brendan@meer.net> wrote in message news:<3E7662AB.4060006@meer.net>...

> What do you mean by default behavior?  The default getProperty and 
> setProperty implementations are stubs that return true.  Can't you just do
> 
>     if (!JSVAL_IS_INT(prop))
>         return JS_TRUE;
>     return ins->setBuiltinProperty(JSVAL_TO_INT(prop), value);
> 
> here?  (I'm pretending setBuiltinProperty returns a boolean indicating 
> error/exception with false.)

Ah, sorry, my terminology is wrong. What I meant was, there doesn't
seem to be a way, when defining property op in a JSClass, to access
the default behaviour of JSObject. I.e, add properties to the object's
map, lookup undefined properties on the prototype, and so forth. So
you can't write 'filtering' property ops, at least as I currently
understand it.

Am I correct, or got the wrong end of the proverbial stick? I've
looked through all the examples I could find, but most people using
JSClass seem to be only using builtin properties.

H&H
James

.