Hi, I'm working on rust bindings to wx, based on the (wonderful!) wxc layer exposed by wxhaskell. When starting on the wxdirect equivalent, it struck me that it was wasteful for everyone to be parsing the .h files - instead, wxc could consist of both the header files and some sort of serialised data structure (e.g. json):
C file: TClassDefExtend(wxTimerEx,wxTimer) void wxTimerEx_Connect( TSelf(wxTimerEx) _obj, TClass(wxClosure) closure ); TClass(wxTimerEx) wxTimerEx_Create( ); TClass(wxClosure) wxTimerEx_GetClosure( TSelf(wxTimerEx) _obj ); parsed data: class: wxTimerEx parent: wxTimer methods: [ { c_fn: wxTimerEx_Connect name: Connect return_type: void args: [[wxClosure, closure]] }, ... ] What do you think? Would this add an unnecessary extra burden? I figure the data structure is in memory at some point anyway, so dumping it to a file shouldn't be too much of a problem. martin ------------------------------------------------------------------------------ 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 _______________________________________________ wxhaskell-devel mailing list wxhaskell-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel