The other day, BrowserUK
mentioned that he felt still a few features were missing from the Perl ithreads implementation. Fortunately, I was able to quickly provide a solution to the feature he was missing (check out Thread::Running
if you're interested).
So far I've recorded these missing features:
- Being able to set the priority of a Perl thread.
- On Win32 this would involve SetPriority and friends, on *nix this would involve nice(). Object is to come up with a transparent interface that would work on both types of systems and would still allow access to all features.
- Find out whether yield() is a no-op or not
- This would allow you to warn the user if a threaded application that uses yield() will burn a lot of CPU or not.
- Suspend/Resume a thread
- It can be useful to be able to create threads and suspend them pending some event. Without knowledge of how threads are implemented on other platforms I can't say much more on this. (suggested by BrowserUK).
- Debugging threads
- Use debugger like you are able to do without threads. (suggested by BrowserUK).
- die(), warn() and Carp.pm include thread information
- Currently, you don't know from which thread a message originated (suggested by BrowserUK)
I was wondering whether maybe other people miss features in Perl threads as well. If you do, please let them know. Maybe something already exists on CPAN that does the trick. Or maybe it is simple to implement and abstractify (is that a word?) into a module.
Any valid suggestions I will add to the above list.