Join GitHub today
wishlist: add Devel::Peek::Dump() support #13
Thanks for the suggestion!
In commit 8fe1580 this is added under the name "info variables dump". There are already other "info variables" commands. I would like to do more on validity checking of the variable name argument, but I don't know to what extent that can be done. I don't know Devel::Peek that well, should more features be offered?
I am happy that Devel::Peek is part of Perl. I'm not happy that Devel::Peek::Dump uses
Some side comments. Look at the commit for how easy it was to hack this in, although it is probably not complete and I should add a test.
commit 21f5bba fixes the help string for the "finish" command that I noticed in the demo. Again, thanks for the NY.pm work and organizing this meetup.
pushed a commit
Aug 23, 2012
On Thu, Aug 23, 2012 at 12:22 AM, R. Bernstein email@example.com:
I suspect a patch to Devel::Peek would get accepted (though it doesn't help
Thanks for a great talk.
I have not been successful in using Capture::Tiny here. It redirects output, but in the process the eval environment is not what is needed. The whole eval in the DB package is really fragile if not also ugly and contorting. For now, there is an "eval-print-save" branch that has this code, but in master, I've disabled this.
Of course running:
works if you want the output to go to STDERR. In general though, this is not what is always desired.
I'll also try to work up a patch for Devel/Peek.xs to add an optional filehandle parameter. Looking at the existing code, that seems the least invasive and backward compatible.
On Thu, Aug 23, 2012 at 11:01 PM, R. Bernstein firstname.lastname@example.org:
Again, this is probably something worth asking about on #p5p and seeing
Ok. Done. Will wait on resolution there on Devel::Peek before adding a command.
Another thing you can do in the meantime is add a macro for this. In
But if you do this, be aware that there was a bug in handling macro parameters that was just fixed 2ccb9c1 . Version 0.34 will have this fix.