Re^4: De-Overload reference?

Please excuse my ignorance, while there are multiple possible approaches for concurrency in Perl, including cpan solutions like Coro I'm not experienced with them.

The race condition I'm worried about is that the overloading might be deactivated when in a simultaneous situation it's expected.

Does your code prove this to be not possible?

Cheers Rolf
_{(addicted to the Perl Programming Language :)

see Wikisyntax for the Monastery}

Comment on Re^4: De-Overload reference?

Replies are listed 'Best First'.
Re^5: De-Overload reference? by choroba (Cardinal) on Apr 17, 2024 at 20:23 UTC
No, I just showed it doesn't happen in threads. I have no expertise in Choro. `map{substr$_->[0],$_->[1]\|\|0,1}[\\|\|{},3],[[]],[ref qr-1,-,-1],[{}],[sub{}^ARGV,3]`	[reply] [d/l]
Re^6: De-Overload reference? by LanX (Saint) on Apr 18, 2024 at 13:22 UTC
Sorry, but how does it show that the overloading works in one thread while it's deactivated in the other one? If those are outputs from different threads, could you append an identifier? Cheers Rolf _{(addicted to the Perl Programming Language :) see Wikisyntax for the Monastery}	[reply]
Re^7: De-Overload reference? by choroba (Cardinal) on Apr 18, 2024 at 13:23 UTC
Each thread outputs something completely different. Threads are not like fork, you specify the code to run in a thread. `map{substr$_->[0],$_->[1]\|\|0,1}[\\|\|{},3],[[]],[ref qr-1,-,-1],[{}],[sub{}^ARGV,3]`	[reply] [d/l]