in reply to Multiple asynchronous execution of commands

threads are not deprecated, they're discouraged. It just means the folks in IRC got fed up with newbies constantly asking how to use threads. If you need an interpreter with thread support, you can compile it yourself, or use perlbrew. 
($q=q:Sq=~/;[c](.)(.)/;chr(-||-|5+lengthSq)`"S|oS2"`map{chr |+ord
}map{substrSq`S_+|`|}3E|-|`7**2-3:)=~y+S|`+$1,++print+eval$q,q,a,

[download]

Replies are listed 'Best First'.
Re^2: Multiple asynchronous execution of commands
by ibm1620 (Hermit) on Jan 22, 2016 at 20:07 UTC
    Thanks for pointing out the distinction. Unfortunately, I'm stuck with whatever build of Perl the operations staff compiles. We're currently on v5.10, which does have thread support built in, but if a future release comes along that omits it by default, I may be out of luck.

    (http://perldoc.perl.org/perlpolicy.html#discouraged states that discouraged features are considered to be "mistakes" that may one day be deprecated.)
[reply]
      Unfortunately, I'm stuck with whatever build of Perl the operations staff compiles. We're currently on v5.10, which does have thread support built in, but if a future release comes along that omits it by default, I may be out of luck.

      Version 5.10 is more than 8 years old. If your ops team keep on this path you'll have a good 8 years to plan your migration away from threads in the unlikely event that it is removed from perl.

      [perldoc] states that discouraged features are considered to be "mistakes" that may one day be deprecated.

      That is true. However, there would be a serious outcry if threads were removed from Perl5, given the amount of code which requires it. And deprecated != removed, so even in a worst-case scenario you'll have plenty of warning.

[reply]

In Section Seekers of Perl Wisdom