On Sat, 14 Aug 2010, Michael Blumenkrantz wrote:
> Having threadsafe data types is useful for anyone using threads. Out > of the people I've asked, nobody has been against adding threadsafe > operations; > the opposite, everyone has been pro threadsafety as desktop cpus are gaining > more cores and thus the ability to efficiently multitask. multitasking ? in the EFL ?? except the internal of evas (which does not require the thread safety for the eina data types), i don't see anywhere else where it is useful. > This is not a null use case. Aside from desktop usage, I am working on > bringing > EFL into secure server operations, and this requires the use of threads. what do you mean by "secure server operations" ? > I realize that not everyone uses threads, which is why threadsafety is in no > way required or enabled for normal operation. as the ecore main loop is not thread safe, and almost all the EFL are not thread safe, the interest is almost 0. You could say that with that thread safety, the EFL will be used with other toolkit like gtk or qt. Such thing will never happen, we know that. Such thread safety is not tested well. It means that we maybe have to fix a lot of bugs, while the release is quite soon. If threadd safety is really needed, better adding them after the release. The code is anyway in svn, so it is not lost. Vincent ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
