Cedric BAIL schrieb:
>>> Putting eina now into cvs doesn't help anyone at the moment. There are two
>>> ways we can go:
>>>
>>> 1. First we start with a little lib, where we put step by step code into it,
>>> we agree with that it belongs into the common lib. That's what I tried with
>>> edt.
>>> 2. We first discuss how the common lib needs to be en bloc and in detail and
>>> then change eina to match the result of the discussion. And move it then
>>> into cvs.
>>>
>>> It looks like most people here prefer the second way.
>>>       
>
> I will say we have a third option. Put a common lib in cvs now. Then
> slowly move stuff around to the new system. With current work from
> caro with Evas_Data.h we should be able to provide a set of macro that
> will help do the move quickly. This move should not impact performance
> at all (and looking at eina current code, I don't see how it could
> change something regarding that).
>   

With focus on evas this is right, but you would be going to make facts 
without discussing them before. For example in eina the evas_hash 
implementation is called eina_hash. I think it'd be better to reserve 
this name for the ecore_hash implementation, because it is much more 
general. For the evas_hash implementation another name like eina_strhash 
would imho then be better. And I'm still not convinced if there is a 
general need to have a fixed-point implementation in the base data types 
lib, just to mention my concerns. Maybe someone else, with more 
authority then me :), will join this discussion.

I'm sure turran took care in doing eina, but you'll get more agreement 
if things are discussed before.

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

Reply via email to