in reply to How to avoid extra DESTROY calls in multi-threaded program?

those errors "HASH(0x101254f4)" is telling you the variable your printing is realy a hash.

"If a reference is used in a context where a string is expected, then the ref function is called automatically to produce the expected string, and a unique hexadecimal value (the internal memory address of the thing being referred to) is appended. That means that printing out a reference:" - Bless My Referents

Good Luck!

Updated: :s

  • Comment on Re: How to avoid extra DESTROY calls in multi-threaded program?

Replies are listed 'Best First'.
Re^2: How to avoid extra DESTROY calls in multi-threaded program?
by chromatic (Archbishop) on Dec 21, 2006 at 19:09 UTC

    I really don't think this is helpful advice. All of the output I saw contained the default stringification of blessed references.

      I agree.