in reply to Re^2: Program Design Around Threads
in thread Program Design Around Threads
I've been planning on doing so for a long time; but whenever I think about doing so, the same problems crop up.
What to call it?
I refuse to add anything to the Thread::* namespace as it is so overpopulated with broken and useless modules.
If I uploaded it to the threads::* namespace I'd almost certainly get nasty emails for using an all lower case element in the name, just like I did when I uploaded my very first module as used.pm.
And then there is the problem of dealing with all the cpan tester failure reports that'll come because it doesn't work on non-threaded builds. (Just like the 75% failure rate that gets shown for Win32::Fmode because it doesn't compile on Linux boxes!).
And then I'd have to figure out the names and locations of all those other files that a cpan distribution must have despite that perl doesn't use them and nobody ever reads them. (And what meaningless drivel to put in them; except for those that have to be empty.)
At this point I usually think to myself: "I'll just point people at that node; it's one text file; stick it in the right place and it just works!"; and move on to something else.
|
---|
Replies are listed 'Best First'. | |
---|---|
Re^4: Program Design Around Threads
by choroba (Cardinal) on Mar 06, 2013 at 23:19 UTC | |
by BrowserUk (Patriarch) on Mar 06, 2013 at 23:26 UTC | |
by choroba (Cardinal) on Mar 06, 2013 at 23:29 UTC | |
by BrowserUk (Patriarch) on Mar 06, 2013 at 23:46 UTC |