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 2 - many modules uses that, like eina itself, ecore and evas. to do path finding, etc. >> On Thu, Dec 6, 2012 at 11:05 AM, Vincent Torri <vincent.to...@gmail.com> >> wrote: >>> >>> Hey >>> >>> as eio is quite used, now, why not deprecating ecore_file parts that >>> are in common with eio ? >>> >>> Vincent >>> > > +1 on the idea tho ;) > > dh > > -- Gustavo Sverzut Barbieri http://profusion.mobi embedded systems -------------------------------------- MSN: barbi...@gmail.com Skype: gsbarbieri Mobile: +55 (19) 9225-2202 ------------------------------------------------------------------------------ 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
