On Mon, 2011-02-28 at 11:42 +0100, Cedric BAIL wrote: > In that case, maybe we should take it from the other side of the > problem. What do we plan to add inside eina and if we need to move > this infra somewhere else. > > I do plan to provide an eina_file_mmap implementation that will > provide infrastructure for file open/fstat/mmap and cache that some > EFL are currently doing locally (Eet, Evas and Efreet come to my mind > as the first users of this feature). > We also have this XML parser. > > So what esle could end in Eina ?
If we are adding an XML parser, why not a Json parser as well? And what about the 123421 other things there are to parse? If we add them, it'll suck, if we don't we'll suck (cause we only support XML in eina, but other stuff in other places). Furthermore, I don't want to encourage people to use XML, but that's just me :P My problem is not with specific functions, but with classes of functions. Is Eina EFL's config/file/whatever parsing library? If not, it shouldn't include it, if so, so yeah, we can add it. One exception is if we want to use XML internally for our config and etc, but then we should probably not expose the XML api. -- Tom. ------------------------------------------------------------------------------ Free Software Download: Index, Search & Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
