On Mon, 6 Jan 2014 13:25:30 +0900 Cedric BAIL <cedric.b...@free.fr> wrote:
> Hello, > > As we move forward with Eo and Eolian, we will generate a part of our > code automatically at compile time (some .c and .h). We also by now > require a C++ compiler (for ephysics) and Lua for Edje. So I am > thinking it is starting to make sense to plan the generation of those > bindings at the compile time of EFL to, instead of relying on another > stage where will would generate those. > > Benefit would be that we do provide support for 3 languages out of the > box when you install the developers package of EFL. We are not adding > a new set of dependency as they are already in. Also we can just parse > Eolian file once and generate all output code at the same time which > will be more efficient and will generate bindings faster than if we > have to do that outside of EFL. > > There is yet no code to really show, except a few discussion on phab, > but they are clearly not ready for integration in our git. The reason > I am bringing it here, is just that Tom wanted a proper place to > troll^Wdiscuss the idea of generating bindings at the same time as we > do compile EFL. > > I am not putting Python or JS in this list as that would indeed > increase the number of dependencies to build EFL which we also don't > want to increase that much anymore. > > So if you see any issue with that idea, please come forth with > arguments. Raster and I have considered using LuaJIT for Edje Lua, and one of the things LuaJIT includes is automatically generating Lua bindings based on C headers. I've not actually played with this yet, but I think it boils down to "we wont need to do much". On the other hand, the first step in auto generating bindings for any language is the same - analyse the existing code and produce some sort of data structure that the following step uses to generate the bindings. This first step should really be done once generically. Then we can support your three languages out of the box, and the rest only have to write the second step. On the gripping hand, I've already written a LSL parser that generates an AST, then outputs Lua code from that. No doubt I can use some of that if the LuaJIT idea doesn't work so well. -- A big old stinking pile of genius that no one wants coz there are too many silver coated monkeys in the world.
signature.asc
Description: PGP signature
------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
