Beefy Boxes and Bandwidth Generously Provided by pair Networks Bob
We don't bite newbies here... much
 
PerlMonks  

Re^3: Program Design Around Threads

by BrowserUk (Pope)
on Mar 06, 2013 at 16:28 UTC ( #1022026=note: print w/ replies, xml ) Need Help??


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.


With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.


Comment on Re^3: Program Design Around Threads
Re^4: Program Design Around Threads
by choroba (Abbot) on Mar 06, 2013 at 23:19 UTC
    Call it Thrum or Funicle. To avoid FAIL messages, just die unless ($Config{usethreads}) in the tests. Use a boilerplate module from CPAN to create all the needed files.
    لսႽ ᥲᥒ⚪⟊Ⴙᘓᖇ Ꮅᘓᖇ⎱ Ⴙᥲ𝇋ƙᘓᖇ
      Call it Thrum or Funicle.

      No thanks.

      To avoid FAIL messages, just die unless ($Config{usethreads}) in the tests.

      A dieing test will prevent FAIL messages?

      Use a boilerplate module from CPAN

      Isn't h2xs easier than renaming all the files as well as editing their contents?

      And then there is still the problem of working out which files are actually necessary; and deciding what irrelevant guff to fill them with.


      With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
      Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
      "Science is about questioning the status quo. Questioning authority".
      In the absence of evidence, opinion is indistinguishable from prejudice.
        A dieing test will prevent FAIL messages?
        I was not accurate. Bail out in tests or die in the Makefile.PL|Build.PL.

        Also read CPAN Author Notes.

        لսႽ ᥲᥒ⚪⟊Ⴙᘓᖇ Ꮅᘓᖇ⎱ Ⴙᥲ𝇋ƙᘓᖇ

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1022026]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others examining the Monastery: (5)
As of 2014-04-20 16:06 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    April first is:







    Results (485 votes), past polls