[webkit-dev] WebKit gobject bindings: Who is guiding their future?
darin at apple.com
Sat Aug 27 23:12:39 PDT 2016
You may have noticed the substantial improvements we’ve made to our WebIDL support over the last year.
The first step in this direction is in <https://bugs.webkit.org/show_bug.cgi?id=161295 <https://bugs.webkit.org/show_bug.cgi?id=161295>>.
I see a few different options, maybe not all real practical ones:
Option 2) Express the list of which functions have a GError** out argument as an explicit list of function names inside the gobject bindings generator and generate code accordingly. This is not all that farfetched given we already have .symbols files to help keep the set of gobject bindings functions stay stable, and there is already a list inside the bindings generator of functions that used to raise exceptions and therefore have a GError** out argument that is never used, showing that this issue is not a new one. Compared to (1) this is just a stopgap measure. It can keep existing functions working, but does not give us a clear path for what to do as we add more and more DOM APIs that don’t fit in with what the gobject binding code generator can do.
Are there other practical options?
I strongly prefer option 1, and I would like to hear from the people who are working to make the gobject bindings work well to get an idea of how they feel about this and how they’d like to proceed, before I decide what to do.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the webkit-dev