Em Seg, 2013-10-28 às 20:17 -0200, Felipe Magno de Almeida escreveu: > The tool that will generate the C++ binding will read the header files > and with a CPP library it wil hook on EO3_DEFINE_* and EO3_DECLARE_* > to read the class informations. This part of the tool will be written > as a C++ library to be reused for other bindings to get the necessary > information for the EFL API through its headers.
Please don't! Please don't make the same mistake of Qt developers. Don't write yet another preprocessing tool. At least, if you are going to write such a tool, write a complete parser that will never have any trouble with #defines and newer syntax and you're willing to maintain it... But... how will your tool know the defines and such things? Probably I'll have to change my build system to call your tool using the same compiler args... I think you're aware that GTK-- is winning from Qt among some C++ developers, because GTK-- is more C++ish than Qt (thanks to moc and other things). -- Vinícius dos Santos Oliveira https://about.me/vinipsmaker
signature.asc
Description: This is a digitally signed message part
------------------------------------------------------------------------------ Android is increasing in popularity, but the open development platform that developers love is also attractive to malware creators. Download this white paper to learn more about secure code signing practices that can help keep Android apps secure. http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk
_______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
