Re^2: Can I/O operations on the same IO::Socket be executed in different threads?

How laughably naive of you to produce code that does nothing useful and announce: "you won't have any problem".

No wonder p5p decided to "discourage" threads when "experts" go around handing out advice like that!

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". I'm with torvalds on this

In the absence of evidence, opinion is indistinguishable from prejudice. Agile (and TDD) debunked

Comment on Re^2: Can I/O operations on the same IO::Socket be executed in different threads?

Replies are listed 'Best First'.
Re^3: Can I/O operations on the same IO::Socket be executed in different threads? by ikegami (Patriarch) on May 13, 2015 at 03:14 UTC
Threads aren't discouraged by p5p. The docs mispeak. It's meant to be a warning on the heavyness of Perl threads. It's already in the process of being fixed.	[reply]
Re^4: Can I/O operations on the same IO::Socket be executed in different threads? by Anonymous Monk on Dec 03, 2020 at 00:13 UTC
Threads aren't discouraged by p5p. The docs mispeak. It's meant to be a warning on the heavyness of Perl threads. It's already in the process of being fixed. Still not fixed 2020-12-02	[reply]
Re^5: Can I/O operations on the same IO::Socket be executed in different threads? by choroba (Cardinal) on Dec 03, 2020 at 10:29 UTC
Feel free to revive the issue. `map{substr$_->[0],$_->[1]\|\|0,1}[\\|\|{},3],[[]],[ref qr-1,-,-1],[{}],[sub{}^ARGV,3]`	[reply] [d/l]
Re^6: Can I/O operations on the same IO::Socket be executed in different threads? by Anonymous Monk on Dec 03, 2020 at 23:39 UTC


Problems? Is your data what you think it is?
	PerlMonks