Vincent Torri schrieb: > > I think that Hisham wants you to put your code in edata, and not create > another lib. > > Unfortunately, it isn't that easy. We have two (or with other counting 3 or 4) list implementations and two hash implementations. Since their API is totally different, especially for the lists, we cannot simply choose one of them and port the rest to that API without an incredibly huge amount of work. So the only way we can handle it is to have both implementations parallel in the data lib. But how are we going to name them? Maybe we name the evas_list edt_nodes or we name the ecore_list edt_slist and the ecore_dlist edt_dlist, so we can use edt_list for the evas_list. For the hashs the situation is a bit better. After Nathan has his ecore_hash improvements in. We can make the evas_hash a wrapper around it. But we still need to think about a name for it, maybe edt_strhash. Where we can really unify stuff is for ecore_list2 and evas_object_list, i think we can take there turran's eina_inlist. And edata has also an edata_array, what are we going to use evas_array or edata_array, or do we also need both? Besides that I wouldn't put ecore_tree into the new lib before it is fixed, it is currently in an unusable state.
As you can see there are many open questions, that needs to be answered first. That's why raster had the idea to first put the string pool into the new lib, because - as mentioned before - the API is the same. Of course we still need to discuss what is going into that lib and how. If people prefer to discuss it yet and do the whole stuff later at once, we can do this as well, but just taking edata doesn't work. I hope that clarify things 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 [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
