On Thu, Dec 6, 2012 at 2:48 PM, Christopher Michael <cp.mich...@samsung.com> wrote: > On 06/12/12 13:40, Gustavo Sverzut Barbieri wrote: >> On Thu, Dec 6, 2012 at 11:38 AM, Christopher Michael >> <cp.mich...@samsung.com> wrote: >>> On 06/12/12 13:25, Gustavo Sverzut Barbieri wrote: >>>> >>>> ecore_file itself should go. >>>> >>>> path manipulation (exists, dirname...) should go in eina, other bits >>>> should go in eio. >>>> >>> >>> Why split file/path functions (exists, dirname, etc) to eina ? If Eio is to >>> be the library for file functions, then why break only "some" of them out >>> into eina ? >> >> two reasons: >> 1 - they are very, very simple. mostly wrappers around system versions > > Well, I think the complexity of the functions is irrelevant as a reason > really. > > Do we typically use, "Well this graphical function is incredibly complex > so it should be broken out from evas and stuck into a different library" > as a basis for development ? Or the converse .. "Well this graphical > function is incredibly simple so it doesn't belong in evas". I don't > think we do development that ;) > > .... IMO, I don't see function complexity as a valid reason here. > >> 2 - many modules uses that, like eina itself, ecore and evas. to do >> path finding, etc. >> > > Ok ...then why can't those libraries use eio ??
if i'm not mistaken, eio uses ecore, so could be a problem for a use in evas Vincent ------------------------------------------------------------------------------ LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
