Howdy, I have created an issue to port the mentioned docs:
https://github.com/parrot/parrot/issues/809 If somebody has suggestions for exactly where these docs should go, please add it to the ticket. Duke On Thu, Aug 2, 2012 at 1:49 PM, Stefan Seifert <[email protected]> wrote: > On Thursday 02 August 2012 15:46:45 Andy Dougherty wrote: > >> For the threads tests, it sure seems like a race condition to me that is >> exposing a weakness in parrot's thread implementation. Last time I >> looked, the tests were relying on sleep() calls. That seems wrong and >> fragile to me. No explicit sleep call should be needed. The threading >> interface ought to supply the necessary functions to ensure things are in >> whatever state the tests are expecting. > > The failing tests are not even threading related. They test callback > functionality of the NCI interface. The reason for them to fail in the threads > branch is that I changed the implementation of sleep() to use the timer > thread. > > The implementation of the timer thread is in src/alarm.c. I'm using the > threading library abstraction makros from the previous threading > implementation. Maybe they do not behave exactly like POSIX on all platforms? > I could only test them on Linux and Windows. > >> For the threads examples, I have no idea what they are actually supposed >> to do -- there's no documentation -- so I was never sure what was supposed >> to be happening with them, and couldn't usefully test them either. > > Sorry, I still haven't come around to add the docs. For the time being, you > can find descriptions in my bachelor thesis at > http://niner.name/Hybrid_Threads_for_the_Parrot_VM.pdf chapter 7 (page 29-31) > > Stefan > _______________________________________________ > http://lists.parrot.org/mailman/listinfo/parrot-dev -- Jonathan "Duke" Leto <[email protected]> Leto Labs LLC http://labs.leto.net 209.691.DUKE http://dukeleto.pl _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
