Bug 28774 - Need a way to expose IDL sequences to ObjC bindings
Summary: Need a way to expose IDL sequences to ObjC bindings
Status: RESOLVED WONTFIX
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebCore Misc. (show other bugs)
Version: 528+ (Nightly build)
Hardware: PC OS X 10.5
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-08-27 09:02 PDT by Andrew Wilson
Modified: 2016-08-04 13:57 PDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Wilson 2009-08-27 09:02:41 PDT 
Currently we expose sequence types via custom getters/setters in the JS bindings that map between the native WebCore collection types and JSArray (for examples, see SQLTransaction.idl and Clipboard.idl).

It seems that the generated ObjC bindings for these files will not compile because the types exposed for these values in the IDL files (Array, ObjectArray) are unknown in ObjC-land.

For now, we just aren't exposing bindings for those files (or, in the case of MessageEvent and the various instances of postMessage(), we are exposing a different set of non-array bindings for ObjC).

When we add support for some kind of array type to the ObjC bindings generator, we should update MessageEvent and postMessage() to expose a uniform API for both sets of bindings.
Comment 1 Anders Carlsson 2016-08-04 13:57:20 PDT 
Obj-C bindings are frozen.