Re^7: ithreads, locks, shared data: is that OK?

It was just an idea. If you have enough time, try all the solutions, benchmark, compare readability. Using shared variables means you need locking, which is complex and can go wrong. Peaking means you need to lock the queries, which slows down the work and introduces locking, which is complex and can go wrong :-)

($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]

Comment on Re^7: ithreads, locks, shared data: is that OK? Download Code

Replies are listed 'Best First'.
Re^8: ithreads, locks, shared data: is that OK? by bliako (Abbot) on Sep 20, 2018 at 16:52 UTC
OK. This is what I wanted to confirm. I think I am on the right track in the sense I am not doing things upside-down, I will experiment with the options. thanks for the advice. bw bliako	[reply]