Anonymous Monk has asked for the wisdom of the Perl Monks concerning the following question:

We have been using perl compiled without thread supports, or "nonthreaded perl" for quite a while. Now I came to know that threaded perl is being used elsewhere. My question is if using threaded perl everywhere would cause problems with code that has never been involved with threads or ever cared about threads.

"threaded perl problems" in Super Search did not bring anything of note; results were related to problems with thread use.

  • Comment on Possible problems of using perl with threads support

Replies are listed 'Best First'.
Re: Possible problems of using perl with threads support
by kcott (Archbishop) on Oct 04, 2013 at 09:45 UTC
    "My question is if using threaded perl everywhere would cause problems with code that has never been involved with threads or ever cared about threads."

    As far as I know, code that doesn't involve threads should run the same whether thread support is compiled or not.

    I have compiled my last 3 or 4 Perls with "-Dusethreads". Code written before that still runs as before. I don't see anything different from what I'd expect with new code that doesn't involve threads.

    -- Ken

      Thank you and another one.

      I did stumble on the problem that multitude of Module::Build tests fail after having built perl 5.16.3 with threads (along with some tests of porting/checkcase.t & porting/podcheck.t). OTOH, all of the tests pass when unthreaded perl is built. Off to file bug report ...

        Test failures were due to reference to path of perl 5.16 sans thread. All the tests passed of perl 5.16.3 compiled with thread support after removing that path reference.
Re: Possible problems of using perl with threads support
by Anonymous Monk on Oct 04, 2013 at 04:35 UTC

    Using a threaded perl, means you can use threads, you need a threaded perl to use threads, without a threaded perl you cannot use threads

    A threaded build of perl won't cause any problems