On Apr 11, 2013, at 5:02 AM, Thiago Marcos P. Santos <[email protected]> wrote:
> Would be great if both projects could share the same generators. The part that would be OK to share would be the parsing. The actual code generation needs to change all the time as the internal architecture of WebKit and of the JavaScript engine and other things we’re binding change, so we should not try to change that. > People writing device API bindings for web runtimes that are injected at > runtime could also use it. I understand, but I think there are different requirements there. For these things injected at runtime we’d want the API to be stable, whereas for inside the project we want the best possible performance even if many implementation details are exposed. WebKitTestRunner does something like this, and do I think that it has requirements very similar to other “injected at runtime” uses. > Would be interesting if we could have the bindings generators as a > separated/standalone project. That does not sound like a good idea to me for the specific reasons I mentioned above. -- Darin _______________________________________________ webkit-dev mailing list [email protected] https://lists.webkit.org/mailman/listinfo/webkit-dev
