On Tue, 2010-10-05 at 09:05 -0300, Iván Briano (Sachiel) wrote: > I think it's a very bad example, considering glib is an outside dependency. > On the other hand, given the amount of functions in the EFL that return an > Eina type, having your app break because you were not explicily initializing > it, > in the case of it being dropped, is probably the least of your worries. > > Yes, I agree that sometimes it's better to be explicit, but generalizing every > case is not always a good idea.
Like I said a couple of emails back: I'm not sure about this specific case, because eina is VERY depended on through all of efl. I was just saying (like as you just said) that sometimes (most of the times) it's better to be explicit. And yes, I agree glib+ecore wasn't a good example, that's why I changed it to ewebkit+glib :P -- 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
