To the statement of being "two many words", I just want to say that I prefer that instead of a brief cryptic answer one might get. You gave me a chance to understand the mechanism around the issue not only the coding part of it. I thanks you for that.
For me, English is not my native language (instead my 2nd) so I apologise for any grammar or typing errors in my posts.
I think I understand your post completely, but something is still bothering me. For example, to start a new thread, you said that almost all memory are copied to the new thread. Just like starting a new instance of the program at that momentary interpreter position.
So unless I explicitly share my variables (is ok) or objects (not ok), these both threads would not know of each other. So why does Perl debugger bother me with that message I've presented in my first post?
If I run the program with the thread starting the empty shell method Update() nothing is then shared and It should not be a problem.
If you think I'm a lost cause in this issue, you can supply me with some good URL:s so I can expand my thread-wisdom further, as the monks would put it.
I have some knowledge in assembly programming with context-switchin with processes but not so much about thread implementations.
We can leave it with that, you have already surpassed my greatest expectations while getting help ;)
Don't know how to repay you but I can at least spread my new gained knowledge to other.
In reply to Re^4: Problem with using threads with modules.
by tele2mag
in thread Problem with using threads with modules.
by tele2mag
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |