A common problem the we're hitting when working on JSC is that the Qt bridge bindings are implemented in terms of JSC internals. This keeps causing us problems as no one working on JSC really knows anything about Qt or the API the bridge objects are intended to provide, and yet we are required to keep them running when making significant changes.
Given there seems to be little focus on these bindings from Nokia it seems that the best path forward is to have them rewritten in terms of the JSC API rather than the JSC internals. This will insulate the bindings from future changes and make life a little easier for everyone. I've filed https://bugs.webkit.org/show_bug.cgi?id=60842 to track this change. If during the conversion people find any short comings in the JSC API that's useful too, as it's likely that those problems would impact other users of the JSC API and we would welcome bugs being filed on those them (CC'ing me :) ). Thanks, Oliver _______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
