On 07/03/16 10:14, Simon Lees wrote: > > > On 03/07/2016 11:08 AM, Tom Hacohen wrote: >> On 07/03/16 04:57, Jean-Philippe André wrote: >>> Hi Tom & q66, >>> >>> >>> Is there any chance we could get rid of the 2 in Eo_Event2 as well? >>> >>> I mean this, in Eo.h: >>> >>> /** XXX: Hack until fixed in Eolian */ >>> typedef struct _Eo_Event Eo_Event2; >>> >>> and its eo counterpart: >>> >>> /* XXX: Hack until Eolian is ready. */ >>> type @extern Eo.Event_Cb: __builtin_event_cb; >>> >> It's only needed because Eolian doesn't do function pointers. We could >> get rid of it (I have an ugly way) if we really wanted, but why do you >> care? You should be using Eo_Event everywhere, the 2 is just for >> internal use. Just so headers will be cleaner? >> >> -- >> Tom >> > Maybe if your not planning on making Eolian ready anytime soon the > comment should be changed to reflect the info in this post :P
Fixed. ------------------------------------------------------------------------------ Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://makebettercode.com/inteldaal-eval _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
