I reserved day 11 (in 5 days) for an article about our new shiny parrot threads on the perl6 advent calendar.
Some people are now reserved about threads (diakopter: "this cannot be safe" http://irclog.perlgeek.de/parrot/2012-12-04#i_6209659), most are very excited (since perl people waited 11 years to finally have native, safe and managed threads), and this would give an excellent opportunity to beat the drum. nqp needs to change their compiler for nqplexpad's, how to access read-write and read-write lexical variables from other threads. If it should be allowed at all, if nqp should create a writer sub in the owners Task automatically (perl6 heavy lifting), or only allow transparent read-only access to the value (as currently). Our lexpad implementation works fine and transparent with the read-only samples. transparent rw not. We need to point to whiteknights gsoc post, nine's thesis, our examples at examples/threads/ and the nqp-rx testcase ext/nqp-rx/t/nqp/67-threads.t vs nqp.git t/nqp/67-threads.t The candidates to write this wordpress article (pure html with linebreaks) are nine, whiteknight and rurban. Please step up, I can do the formatting and publishing. Preview my post for day 7 (tomorrow) https://gist.github.com/4226700 (raw html) -- Reini Urban http://cpanel.net/ http://www.perl-compiler.org/ _______________________________________________ http://lists.parrot.org/mailman/listinfo/parrot-dev
