On Sun, Dec 30, 2012 at 12:55 PM, Lucas De Marchi <lucas.demar...@profusion.mobi> wrote: > I don't want to be the boring guy complaining on this. But I can't > agree neither on the reasons why this went in, nor how it went in. For > me eo is just raping C and all the problems pointed out should be > fixed elsewhere.
Please describe how. For example how do you plan to link cleanly any object from ecore or eio for example with any evas_object ? How do you plan to give memory compaction ? How do you see we could do the ID indirection ? How can we do a live debug of live object in a program ? How do you provide multiple inheritance ? How do you provide API and ABI stability over time ? How do you make bindings easier to keep in sync possible ? Please share your idea. If you dislike Eo so much, you must have an alternative in mind that solve the same issue that Eo solve. At the moment, I only see rants and no care about the problem that Eo address and the answer we have been giving here. -- Cedric BAIL ------------------------------------------------------------------------------ Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. ON SALE this month only -- learn more at: http://p.sf.net/sfu/learnmore_123012 _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
