On Tue, Jul 13, 2010 at 5:25 PM, Vincent Torri <vto...@univ-evry.fr> wrote: > > > On Tue, 13 Jul 2010, Gustavo Sverzut Barbieri wrote: > >> On Tue, Jul 13, 2010 at 5:03 PM, Vincent Torri <vto...@univ-evry.fr> >> wrote: >>> >>> Hey, >>> >>> pthread_exit is used with a string, while its parameter is actually the >>> returned value of the terminated thread. >>> >>> for an example: >>> >>> >>> http://publib.boulder.ibm.com/iseries/v5r1/ic2924/index.htm?info/apis/users_18.htm >> >> It's any pointer (void *data) and just of interest if you do a >> pthread_join(), where do you see such incorrect use? > > as the subject says, in eet unit tests, searc pthread_exit in eet_suite.c
Reviewed it, the code is perfectly correct: - on success, returns NULL - on error, returns message as const char * - pthread_join() checks for the thread_ret, if it is NULL it says success (as above), on error it shows the error message returned by thread Where is the error? I can't see it. -- Gustavo Sverzut Barbieri http://profusion.mobi embedded systems -------------------------------------- MSN: barbi...@gmail.com Skype: gsbarbieri Mobile: +55 (19) 9225-2202 ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
