Peter Wehrfritz schrieb: > Yesterday we had a discussion on irc, if we should put abstract data > types of ecore and of evas into a single standalone lib. The whole > discussion came up because of the two implementations of the shared > strings. And in fact if we really want to share strings efficient, we > have to share them over the borders of the different libraries. > > Raster's idea was to first put the shared string stuff in this new > library because both implementation have the same api (of course the > names are different) and the same functionality. Remains the question > which implementation we use. > I've put now the evas stringshare code into a standalone lib. I know that Nathan is working on improving ecore_hash, so that ecore_string becomes faster. We can still change the code later, since the API and ABI remains the same. I called that lib "edt" for "enlighten data types". If you prefer another name I can change it easily. It isn't much work at that point. I also can change the function names they are now:
edt_stringshare_init edt_stringshare_shutdown edt_stringshare_add edt_stringshare_del If you like it, i can commit it. Next step would be to make ecore and evas depend on edt. And make their functions to be only wrappers around edt's one. And then we can replace step by step the names in the libs and apps. You can find the lib here: www.mowem.de/e/edt.tar.gz Kind Regards Peter ------------------------------------------------------------------------- Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
