I retract my earlier statement. I think that the constraints here between WebKit and blink are different enough that we should only re-examine sharing code after both projects have had a chance to re-write this subsystem to better fit their needs. We originally imported these bindings generators from KDOM (and changed them quite a bit), but I suspect that they were never really a perfect fit for WebKit in the first place.
Since we're both theoretically parsing WebIDL here, presumably there are several good parsers already. If both WebKit and Blink choose the same language to re-write their respective bindings generators in, perhaps we'll end up using the same parser library. Best of luck! On Wed, Apr 10, 2013 at 3:36 PM, Eric Seidel <e...@webkit.org> wrote: > I know some folks in our TOK office have expressed strong interest in > re-writing it in python for Blink. Perhaps there is an opportunity > for some x-project collaboration here. > > On Wed, Apr 10, 2013 at 3:32 PM, Ryosuke Niwa <rn...@webkit.org> wrote: >> Hi, >> >> Can we rewrite CodeGenerator*.pm in Ruby or Python? I feel that the current >> code is very hard to understand and hack on. In particular we have >> CodeGenerator.pm and CodeGeneratorJS.pm (CodeGeneratorV8.pm has been >> removed), and we need to merge them anyway. >> >> I've seen many people expressing their inability to improve the binding code >> because of its being written in Perl. >> >> I'm not necessarily volunteering to do the work myself at this moment but I >> wanted to see if there is any interest in this idea or not. >> >> - R. Niwa >> >> _______________________________________________ >> webkit-dev mailing list >> webkit-dev@lists.webkit.org >> https://lists.webkit.org/mailman/listinfo/webkit-dev >> _______________________________________________ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
