When working with threads, try to keep the number of global variables minimal
Why? While that's good advice in general — it's easier to make sure that local variables are in the proper state than it is for global variables — I don't see why it's important for threads specifically. I can see this being an issue for *shared* variables (since their access needs be controlled by locks), but other package, lexical, global and local variables are per-thread by default.
In reply to Re^2: Threads and LWP::UserAgent question
by ikegami
in thread Threads and LWP::UserAgent question
by gatito
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |