in reply to Re^3: eval something using private copy of variables
in thread eval something using private copy of variables

This particular swine thanks you for your Perl wisdom! I didn't know of the concept of Perl threads but they seem perfect for my application.

Of course copying the whole symbol table seems like overkill, but this is for a resource-light calculator program, so the extra time and memory involved seems fine e.g. it took 8K-15K microsec for repeat runs of one simple threaded test vs 70-150 microsec for unthreaded. Waiting .015 sec or so for an answer from a calculator seems acceptable. Since Perl cleans up threads after use, all should be well even if the calculator is left running for a long time.

  • Comment on Re^4: eval something using private copy of variables

In Section Seekers of Perl Wisdom