[webkit-dev] when can I treat a JSValueRef as a JSObjectRef?

2009-05-04 Thread Patrick Mueller
Since JSValueRef and JSObjectRef are typedef's to the same OpaqueJSValue structure (pointer), it appears you could almost use them in the same contexts. And if fact, it appears you can use a JSObjectRef wherever a JSValueRef is defined in the API. And you can sometimes use a JSValueRef

Re: [webkit-dev] when can I treat a JSValueRef as a JSObjectRef?

2009-05-04 Thread Darin Adler
On May 4, 2009, at 10:17 AM, Patrick Mueller wrote: Since JSValueRef and JSObjectRef are typedef's to the same OpaqueJSValue structure (pointer) It’s easy to get the wrong idea about this by looking at the implementation. These two typedefs use the same structure, but they use const in

Re: [webkit-dev] when can I treat a JSValueRef as a JSObjectRef?

2009-05-04 Thread Patrick Mueller
Darin Adler wrote: What documentation were you reading? Since WebKit is an open source project, if you have improvements to, say, the comments in the header, you can submit them as a patch. Most of the mechanics are covered at http://webkit.org/coding/contributing.html, although some of the

Re: [webkit-dev] when can I treat a JSValueRef as a JSObjectRef?

2009-05-04 Thread Darin Adler
On May 4, 2009, at 10:53 AM, Patrick Mueller wrote: The docs I was reading were in fact the Apple docs I believe the document you cited is automatically generated from the comments in the JavaScriptCore headers. So if we improve the documentation comments in the headers in the WebKit open