As repellent has pointed out, the way to get Devel::Peek::Dump to write to a string is to redirect STDERR to a string. However, if you are running on certain *nixes (Debian-Etch/Perl 5.8.8 and possibly others), the first time you call Devel::Peek::Dump whilst STDERR is redirected to a string, you may see a "Use of uninitialized value in subroutine" warning. This warning does not seem to appear on Windows (so saith ikegami who tried it on Windows for me).
As near as we could tell, this a bug in Devel::Peek::Dump. It has been reported and ticketed as bug 63498. The bug is rated low severity, so you may have to wait a while before this particular annoyance goes away.
Best, beth
Update: more clearly identified systems with potential problems
In reply to Re: Devel::Peek output to a string?
by ELISHEVA
in thread Devel::Peek output to a string?
by perl5ever
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |