On Tue, 1 Mar 2016 09:05:06 +0000 Tom Hacohen <t...@osg.samsung.com> wrote:
> The Eo syntax is going to be changing once more, and this time, I > really think/hope it'll be the last time. We plan on stabilizing Eo > and all of the functions on top of it in the next few months, so that > doesn't leave us much more time to change it again. :) > > These changes will remove the need for the eo_do family of functions. > Functions will now look like normal C functions (which they are). > There are many benefits to that, and we have many cool new ideas. "The new proposed API makes Eo calls look like normal C functions (they are in fact normal c functions)," I thought one of the purposes of eo_do() was to only have one function call + object pointer pass to do several things at once on that object? I've been making a bit of use out of that, rearranging code a little sometimes to take advantage of it. I even thought eo_do() was a good syntax. It works a bit differently to normal function calls, it should look different. Less repetitive typing of my_fancy_object_name. -- 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
------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
_______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
