On Sep 10, 2009, at 5:32 PM, Drew Wilson wrote:
On Thu, Sep 10, 2009 at 5:29 PM, Oliver Hunt <oli...@apple.com> wrote:
This is incorrect, from the bindings point of view the type here
should be "any", which in the JS bindings means ScriptValue. The
actual serialisation is by definition bindings dependent, be that
JSC or ObjC.
Certainly, from a WebIDL standpoint this is correct. I'm not certain
that our current code generator will accept this (the JS bindings
are quite flexible especially if we are talking about custom
attributes, but my experience with the ObjC generated bindings are
that you need to specify concrete classes in the .idl files or else
you end up with type errors at compile time - this could obviously
be changed).
The implementation i had many months ago worked more or less correctly
for obj-c and js (for those objects it could correctly serialise, per
my prior email exactly what got serialised was less clear than would
be ideal) provided that they provided a serialisation function.
--Oliver
_______________________________________________
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
