Hello everyone, I was just investigating some things for Eolian this morning and came to an interesting realization: the function signatures of legacy API have changed over the "classic" legacy API (and as far as I'm aware, we've made a few releases with that already).
Particularly, all legacy API funcs take "Eo*" type as a first argument, instead of the appropriate typedef (such as Evas_Object*). That shouldn't really be the case. The question here is: should an effort be made to fix this for 1.11 release, or should it be dealt with later, or does it need a fix at all? The APIs will still work even this way, but it's likely pretty confusing for legacy API users - the legacy API shouldn't really be using Eo types in function prototypes. I've been trying to figure out a proper fix for this in my branch while solving another problem, but no luck yet - one thing I was trying to do was have Eolian generate an appropriate typedef in each header, but that is met with lots of conflicts (and if I remove some of the old typedefs, they're missing elsewhere)... so... what do? D5 ------------------------------------------------------------------------------ Infragistics Professional Build stunning WinForms apps today! Reboot your WinForms applications with our WinForms controls. Build a bridge from your legacy apps to the future. http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
