On Sun, Jun 29, 2008 at 7:15 PM, Vincent Torri <[EMAIL PROTECTED]> wrote: > I am planning to reorganize the header files of evas, which is a big fat > mess. Then I remembered a discussion on the ML about data types in evas and > ecore, and their respective performance.
> So I'm wondering if, before reorganising the header files, it would be a > good idea to extract from Evas.h all the structures and functions related to > evas data types (array, hash, list and stringshare, but not obecjt_list), > and put them in Evas_Data.h. I would also put Evas_Bool in it as it is > needed by some function and as I want to make Evas_Data.h stand-alone. > I've attached a patch and the Evas_Data.h file > > there is no specific library for those evas data types with that patch. It's > only a move of the api from Evas.h to Evas_Data.h > > Some questions, now: > > * is it really useful to put stringshare there ? Yes, evas stringshare is something you really want, and it's part of the data type. > * should I create a specific lib for data types ? or should the users link > against evas to use them ? I prefer the first solution. I think that at some point we will have the first solution, but doing first the split, will give us an easier path for a data type library. So I am all for this split. -- Cedric BAIL ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
