Re^2: Modification of read-only value

I'm not sure how much less code it would be with threads since threads don't easily share data between them, and I need to pull all the data from all the subprocesses back together at the end. So I'd be exchanging one large chunk of code for another. In general, I'm more familiar with IPC::Open3 and IO::Select than ithreads, so I chose this way due to familiarity. Now, if that's the only option I have for eliminating this intermittent issue, I'm more than willing to try it, but it'll be hard to prove ;-)

As for upgrading perl, I thought I addressed that in the original node. I will be pursuing the upgrade of perl, regardless of this issue, anyway. But it'll take time to get through all the lawyers and managers.

Comment on Re^2: Modification of read-only value

Replies are listed 'Best First'.
Re^3: Modification of read-only value by onelesd (Pilgrim) on Jun 13, 2011 at 22:23 UTC
By all means, go with what's comfortable. I didn't really grok all your code, but personally I hate thread management, and I like that "threads" takes care of a lot of that for you. And, "threads::shared" handles the passing and locking of shared data quite well. I saw you mention the perl upgrade issue in your OP - I kicked it again because I've had intermittent thread issues in the past that simply disappeared by upgrading perl from 5.8 to 5.12.	[reply]

Replies are listed 'Best First'.

Re^3: Modification of read-only value
by onelesd (Pilgrim) on Jun 13, 2011 at 22:23 UTC

By all means, go with what's comfortable. I didn't really grok all your code, but personally I hate thread management, and I like that "threads" takes care of a lot of that for you. And, "threads::shared" handles the passing and locking of shared data quite well.

I saw you mention the perl upgrade issue in your OP - I kicked it again because I've had intermittent thread issues in the past that simply disappeared by upgrading perl from 5.8 to 5.12.

[reply]