On Tue, 2010-10-05 at 21:56 +0800, Tom Haste wrote: > I figured Id throw my $0.00002 AUD into this... > > Being a noob to the programming game, Just the ecore_init() seems fine > by me as long as ecore_init() documentation also states that > eina_init() happens with it. Seeing eina_init() and ecore_init() tells > my noobie brain that one must happen before the other otherwise stuff > might not work right.
I already commented on that, docs aren't everything. Let's assume for a moment ecore does not want to use Eina anymore (but keeps API the same), eina_init() is dropped from ecore_init() (because it's not used) and the docs are updated to state that eina_init() is no longer automatically issued. In this scenario, an application with an explicit eina_init() will continue to work just as well, while an application without the explicit eina_init() will not. Both were written before the change in ecore, and both read in the docs that eina_init() *is* automatically issued. Do you get my point now? -- Tom. ------------------------------------------------------------------------------ Beautiful is writing same markup. Internet Explorer 9 supports standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. Spend less time writing and rewriting code and more time creating great experiences on the web. Be a part of the beta today. http://p.sf.net/sfu/beautyoftheweb _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel