On Tue, 2010-10-05 at 09:41 -0300, Iván Briano (Sachiel) wrote: > Still not good. There's a difference of relying on some component initializing > a library because it uses internally, and initializing it because it's > also giving > you back stuff from it. In the first case, yes, relying on that and not being > explicit can cause you problems in the future, but for the second, even if > Ecore can be built without Evas, ecore_evas_init() is pretty much guaranteed > to init Evas as well, unless something is very wrong somewhere. So being > explicit or not depends on you knowing what you are doing, which doesn't > necessarily imply that you know the internals of what you are using.
ecore_init() says nothing about eina in any way or form. It's not like ecore_evas_init() which explicitly says "evas is there and will be used". As I said, this case is different because ecore will probably always use eina, but still, you can't say ecore_init() implies eina_init() will also be run. But yes I agree that libs that fall under this category: "Still not good. There's a difference of relying on some component initializing a library because it uses internally, and initializing it because it's also giving you back stuff from it." Are special cases (which ecore may be one of those, I'm not sure, I don't remember ecore's API by heart). -- 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
