On 02 Mar 2014, at 18:38, Christian Walde <walde.christian@gmail.com> wrote: > On Sun, 02 Mar 2014 12:15:55 +0100, Elizabeth Mattijsen <liz@dijkmat.nl> wrote: >> Additionally, maybe it would be an idea to mention the forks.pm module on CPAN as an alternative on non-Windows systems? It provides an almost identical threads API (last time I checked), without the disadvantage of the copying needed to start a thread. Since forks.pm uses fork() to start a new thread, it uses the OS’s COW system to copying things only when needed. This results in faster thread starts and lower memory consumption. At the expense of slower inter-thread communication (such as updating shared variables). > > I've been told by people that you're quite experienced with threads. Would you consider writing perlasynctut.pod which discusses the various ways with which one can do asynchronous programming (events, green threads, threads, multiprocessing) in Perl, so the thread documents can point at that? I’m sorry, but I don’t do much anymore, let alone Perl 5. If I would spend the tuits on writing such a document, I would prefer to write one for Rakudo Perl 6 instead. LizThread Previous | Thread Next