On Wed, Sep 7, 2016 at 8:35 AM, Carsten Haitzler <ras...@rasterman.com> wrote:
> On Wed, 7 Sep 2016 10:44:33 +0100 Tom Hacohen <t...@osg.samsung.com> said:

...

>> Shared object and recursive wrapping: I'm not really sure I get what you
>> were talking about, but if I understand correctly it sounds unnecessary.
>> People should manage their own mutexes when sharing objects between threads.
>
> why? even so eo_base would have to do it for itself ANYWAY and then every 
> class
> above that at every entry point put a lock and unlock. it's error prone and
> lots of work. since we have a single dispatch point for methods provided by eo
> we can put it there. the mutex HAS to be recursive tho to work and eina mutxes
> right now are NOT recursive. (well on windows they are as windows mutexes are
> recursive out of the box by default).

AH, THIS THING :-D


-- 
Gustavo Sverzut Barbieri
--------------------------------------
Mobile: +55 (16) 99354-9890

------------------------------------------------------------------------------
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to