On Fri, 29 Jul 2011, Mike McCormack wrote:

> On 07/28/2011 09:31 PM, Cedric BAIL wrote:
>
>> Before providing a benchmark, please revert your broken code and
>> provide a working solution based on my discussion with gustavo (using
>> Ecore_Pipe). Right know, and before doing benchmark, your solution
>> doesn't work in all case and that's a no go for me. It's already
>> painfull for us when we use thread that I don't want to dig why some
>> user have weird behaviour due to this half working solution.
>
> Hi Cedric,
>
> I haven't gotten any mail to Gustavo from you.  Please resend it.
>
> What is broken?  Which case does it not work for?
>
> My code adds a single mutex, which only ecore can see.
>
> The rules for use are fairly simple:
> * lock the mutex on entering ecore code
> * unlock the mutex on leaving ecore code
> * don't call functions that lock the mutex from within ecore
>
> Secondly, this code is disabled, so it shouldn't affect anything right now.
> As I understand, it's normal in EFL development to add code that is disabled,
> debug it, then enable it later when it works.

no. It's not normal at all.

Vincent

------------------------------------------------------------------------------
Got Input?   Slashdot Needs You.
Take our quick survey online.  Come on, we don't ask for help often.
Plus, you'll get a chance to win $100 to spend on ThinkGeek.
http://p.sf.net/sfu/slashdot-survey
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to