Okay. The almost certain cause of the panic:COND_DESTROY message is because you are defining thread functions inside other functions. Here:
sub GETSHIT { sub workder { $ips = shift; ...
And here:
sub asama4 { # ok i'm getting and printing of the array (@REVERSESITES) element +s , lock() is working print $_,"\n" for @REVERSESITES; $getnumm = scalar @REVERSESITES; $Progress_bars->SetRange(0,$getnumm); sub workerss { my $urladdr = shift; ...
But, your code is so badly written and formatted that I am not prepared to expend any energies on trying to fix it.
My advice to you is that you should either: a) start with a simpler project and learn to write clean, structured code before you attempt something as complex as this; or b) employ a proper programmer to write this for you.
Have you ever watched one of the TV game-shows where they bring in an expert pizza maker or master potter or similar, and have them demonstrate their skills for about 2 minutes; before asking one or more of their victims contestants to try and replicate what the expert did?
Of course, as expected, the contestants end up covered in pizza dough/wet clay and offer up an unrecognisable pile of something for the expert to judge. In this context, your posted code is that unrecognisable pile of something. Sorry if that is harsh, but not everyone is cut out to be a programmer.
If you posted a new version that was properly indented and compiled with strict & warnings, I might take another look, but as is:
I'm not prepared to expend any more of my time on it.
In reply to Re^5: thread::share problem
by BrowserUk
in thread thread::share problem
by merlol
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |