Re: lock with references

[BrowserUk]

in reply to lock with references

I can honestly say that I don't remember encountering any particular limitations with using references to shared variables, nor can I intuit anything obvious why they shouldn't be just fine.

However, I also cannot remember any good reason for using references to shared variables.

And a quick search of my source files didn't turn up any obvious examples, but then it is a little hard to search for.

So both my instincts and experience are telling me that whilst I cannot see any particular reason for doing it, it should be just fine....

...but then comes this feeling that if you hadn't encountered some anomaly, you wouldn't be asking...

so, maybe I'll just keep quiet rather than get seen to be caught out by a sucker punch.

[ISAI student]

Relax, I have yet to encounter one, and not into punching anyone. I am doing major rework on a huge script, and trying to make the code more modular, w/o changing the basic algorithm. Hence, passing hundreds of lines of code to some subroutines, which setup shared variables. I have to use references, as two or more shared hashes are changed in 1 chunk of code, and seperating the commands is far too time consuming. I have never worked with threads, and was afraid of some unknown (to me) "gotcha". perlmonks is, IMHO, one of the best place to ask about this, with regards to PERL, of course.

[BrowserUk]

I have to use references, as two or more shared hashes are changed in 1 chunk of code, and seperating the commands is far too time consuming....I have never worked with threads,...

I've done lots of work with threads; and that first sentence makes no sense to me at all.

Are these references, references to shared scalars as indicated in your first post?

Or references to hashes as implied here?

Or possibly references to scalars that are values in a shared hash?

Or references to shared scalars that are values in a non-shard hash?

Or...?