On Tue, 7 Jun 2011, Ulrich Eckhardt wrote:
> On Tuesday 07 June 2011 22:53:59 Vincent Torri wrote: >> It's nice to see someone interested in the win32 code :) > > Thank you for writing it! Actually, I'm interested in the WinCE port even, > because that's the platform I work with for a living, doing embedded > programming in an industrial environment. Hooo, that's nice for the windows ce port if I have some help. In case you don't know : http://trac.enlightenment.org/e/wiki/EFLWindowsCE >> Honestly, i'm not good at all with threads, pthreads or wthreads. Does >> pthread_join() automatically destroy its first parameter (the calling >> thread) when it returns ? > > It's not explicitly stated in the manpages I have, but there's these > statements: > > 1. "Joining with a thread that has previously been joined results in undefined > behavior." > > This seems to imply that the handle (pthread_t) has become unusable, similar > to the pointer given to free(). > > > 2. "Failure to join with a thread [...] produces a "zombie thread". Avoid > doing this, since each zombie thread consumes some system resources[...]" > > This seems to imply that pthread_join() releases all resources associated with > the thread, again similar to free(). > > > That's also why I thought that there should be a free() in that function. The > CloseHandle() on the thread handle is just one part of the cleanup. ok, i'll free it, then. thank you Vincent ------------------------------------------------------------------------------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
