Devel::Kit - Handy toolbox of things to ease development/debugging.
This document describes Devel::Kit version 0.82
use Devel::Kit; # strict and warnings are now enabled d($something); # d() and some other useful debug/dump functions are now availble! perl -e 'print @ARGV[0];' # no warning perl -e 'print $x;' # no strict error perl -MDevel::Kit -e 'print @ARGV[0];'# issues warnings: Scalar value @ARGV[0] better written as $ARGV[0] … perl -MDevel::Kit -e 'print $x;' # Global symbol "$x" requires explicit package name … perl -MDevel::Kit -e 'd();d(undef);d("");d(1);d("i got here");d({a=>1},[1,2,3],"yo",\"howdy");ud("I \x{2665} perl");bd("I \xe2\x99\xa5 perl");gd("I ♥ perl");'
See where you are or are not getting to in a program and why, for example via this pseudo patch:
+ d(1); + d(\$foo); bar(); if ($foo) { + d(2); … } else { + d(3); … } + d(4);
If it outputs 1, $foo’s true value, 3,4 you know to also dump $foo after bar() since it acts like bar() is modifying $foo (action at a distance). If $foo is false after the call to bar() then you can add debug statements to bar() to see where specifically $foo is fiddled with.
Visually see if a string is a byte string or a Unicode string:
perl -MDevel::Kit -e 'd(\$string);'
If it is a Unicode string the \x{} codepoint notation will be present, if it is a byte string it will not be present:
[dmuey@multivac ~]$ perl -MDevel::Kit -e 'd(\"I \x{2665} perl");' debug() ref(SCALAR(0x100804fc0)) at -e line 1: \"I \x{2665} perl" [dmuey@multivac ~]$ perl -MDevel::Kit -e 'd(\"I ♥ perl");' debug() ref(SCALAR(0x100804fc0)) at -e line 1: \'I ♥ perl' [dmuey@multivac ~]$ perl -MDevel::Kit -e 'd(\"I \xe2\x99\xa5 perl");' debug() ref(SCALAR(0x100804fc0)) at -e line 1: \'I ♥ perl' [dmuey@multivac Devel-Kit]$ perl -Mutf8 -MDevel::Kit -e 'd(\"I ♥ perl");' debug() ref(SCALAR(0x100804ff0)) at -e line 1: \"I \x{2665} perl" [dmuey@multivac Devel-Kit]$
From one line data dumping sanity checks to debug print statements in a large body of code I often found myself reinventing these basic solutions.
Hence this module was born to help give a host of functions/functionality with a minimum of typing/effort required.
Any modules required for any functions are lazy loaded if needed so no need to manage use statements!
This is a handy alias I put in my shells’ profile/rc file(s) to make short debug/test commands even shorter!
alias pkit='perl -MDevel::Kit'
Then you can run:
pkit -e 'vd("I ♥ perl");' pkit -Mutf8 -e 'vd("I ♥ perl");'
To get a better ci():
alias pkit_ops='perl -mDevel::CountOps -MDevel::Kit'
You'll probably note that every thing below is terse (i.e. not ideally named for maintenance).
That is on purpose since this module is meant for one-liners and development/debugging: NOT for production.
import() enables strict and warnings in the caller unless you pass the string “no” to import().
use Devel::Kit; # as if you had use strict;use warnings; here use Devel::Kit qw(no); # no strict/warnings perl -MDevel::Kit -e 'print @ARGV[0];print $x;' # triggers strict/warnings perl -MDevel::Kit=no -e 'print @ARGV[0];print $x;' # no strict/warnings happen
If you already have a function by these names you can pass "_" to import() which will import them all w/ an underscore prepended. You can pass "__" to have it prepend 2, "___" to prepend 3, ad infinitum.
You can get a lazy loaded and reused App::Kit object via a().
pkit -e 'd( a->ctype->get_ctype_of_ext(".pm") )'
Takes zero or more arguments to do debug info on.
The arguments can be a scalar or any perl reference you like.
It’s output is handled by "Devel::Kit::o()" and references are stringified by "Devel::Kit::p()".
Runs the given code ref and takes some measurements.
perl -MDevel::Kit -e 'ci(sub {…})' perl -MDevel::Kit -e 'ci(sub {…},1)' # … also include a diff of the symbol table before and after running
Caveat: Observer effect
Some things might not be apparent due the current state of things. For example, a module might be loaded by the coderef but since it is already loaded it is not factored in the results.
Caveat: You get more accurate results if Devel::CountOps is loaded during BEGIN before you call ci()
You could use the pkit_ops alias or -mDevel::CountOps first:
perl -mDevel::CountOp -MDevel::Kit -e 'ci(sub {…})'
perl -MDevel::Kit -e 'ni('Foo::Bar')' perl -MDevel::Kit -e 'ni('Foo::Bar',1)' # … also include ci() info (via system() to cut down on the 2 caveats noted for ci()) perl -MDevel::Kit -e 'ni('Foo::Bar',2)' # … also include verbose ci() info (via system() to cut down on the 2 caveats noted for ci())
perl -MDevel::Kit -e 'ei()' perl -MDevel::Kit -e 'ei(1)' # … also dump %ENV perl -MDevel::Kit -e 'ei(2)' # … also dump %Config
like Devel::Kit::p() but w/ Devel::Size and/or Devel::Peek info as well
perl -MDevel::Kit -e 'ri($your_ref_here)'
perl -MDevel::Kit -e 'si(@system_cmd)'
Execute’s @system_cmd, displays its output labeled as STDOUT/STDERR, and describes its child error and errno states.
Currently there is no interface to the command’s STDIN but it could be added, let me know if you’d find that useful.
Lazy loaded Regexp::Debugger::rxrx() wrapper. See Regexp::Debugger for more info.
perl -MDevel::Kit -e 'rx()'
If a function ends in “d” it is a dumper. Each takes one argument, the string in the format we’re dumping.
Like d() it’s output is handled by "Devel::Kit::o()" and references are stringified by "Devel::Kit::p()".
perl -MDevel::Kit -e 'yd($your_yaml_here)'
perl -MDevel::Kit -e 'jd($your_json_here)'
perl -MDevel::Kit -e 'xd($your_xml_here)'
perl -MDevel::Kit -e 'sd($your_storable_here)'
perl -MDevel::Kit -e 'id($your_ini_here)'
perl -MDevel::Kit -e 'md($your_message_pack_here)'
perl -MDevel::Kit -e 'pd($your_stringified_perl_structure_here)'
These dump information about the path given.
perl -MDevel::Kit -e 'fd($your_file_here)'
perl -MDevel::Kit -e 'dd($your_directory_here)'
perl -MDevel::Kit -e 'ld($your_symlink_here)'
These can take a utf-8 or Unicode string and show the same string as the type being requested.
perl -MDevel::Kit -e 'ud($your_string_here)'
perl -MDevel::Kit -e 'bd($your_string_here)'
perl -MDevel::Kit -e 'gd($your_string_here)'
perl -MDevel::Kit -e 'vd($your_string_here)' perl -MDevel::Kit -e 'vd($your_string_here, 1)' # verbose flag shows Devel::Size and/or Devel::Peek info as possible
Unicode strings are turned into utf-8 before summing (since you can’t sum a Unicode string)
perl -MDevel::Kit -e 'ms($your_string_here)'
perl -MDevel::Kit -e 'ss($your_string_here)'
perl -MDevel::Kit -e 's2($your_string_here)'
perl -MDevel::Kit -e 's3($your_string_here)'
perl -MDevel::Kit -e 's5($your_string_here)'
Unicode strings are turned into utf-8 before operating on it for consistency and since some, if not all, need to operate on bytes.
perl -MDevel::Kit -e 'be($your_string_here)' perl -MDevel::Kit -e 'bu($your_base64_here)'
perl -MDevel::Kit -e 'ce($your_string_here)' perl -MDevel::Kit -e 'cu($your_crockford_here)'
perl -MDevel::Kit -e 'xe($your_string_here)' perl -MDevel::Kit -e 'xu($your_hex_here)'
xe() takes a second boolean arg that when true dumps it as a visual mapping of each character to its hex value.
perl -MDevel::Kit -e 'ue($your_string_here)' perl -MDevel::Kit -e 'uu($your_uri_here)'
perl -MDevel::Kit -e 'he($your_string_here)' perl -MDevel::Kit -e 'hu($your_html_here)'
perl -MDevel::Kit -e 'pe($your_string_here)' perl -MDevel::Kit -e 'pu($your_punycode_here)'
perl -MDevel::Kit -e 'qe($your_string_here)' perl -MDevel::Kit -e 'qu($your_quoted_printable_here)'
perl -MDevel::Kit -e 'se($your_string_here)' perl -MDevel::Kit -e 'su($your_escaped_for_perl_string_here)'
Feel free to override these with your own if you need different behavior.
Outputs the first and only arg.
Goes to STDOUT and gaurantees it ends in one newline.
Returns a stringified version of any type of perl ref() contained in the first and only arg.
Errors are output in the various dumps.
Devel::Kit requires no configuration files or environment variables.
Import::Into for the strict/warnings.
String::UnicodeUTF8 for string fiddling
Module::Want to lazy load the various parsers and what not:
It includes 2 sub classes that can be used as guides on how to create your own context specific subclass:
Devel::Kit::TAP for testing context (using a function based output).
Devel::Kit::cPanel for cPanel context (using a method based output).
None reported.
No bugs have been reported.
Please report any bugs or feature requests to bug-devel-kit@rt.cpan.org, or through the web interface at http://rt.cpan.org.
bug-devel-kit@rt.cpan.org
auto-detect and switch to correct subclass
*d() functions could use corresponding d*() functions (e.g. dy() would dump as YAML …)
Stringified Data dumpers also take path or handle in addition to a string.
string parser/dumpers make apparent what it was (i.e. YAML, XML, etc)
Daniel Muey <http://drmuey.com/cpan_contact.pl>
<http://drmuey.com/cpan_contact.pl>
Copyright (c) 2012, Daniel Muey <http://drmuey.com/cpan_contact.pl>. All rights reserved.
This module is free software; you can redistribute it and/or modify it under the same terms as Perl itself. See perlartistic.
BECAUSE THIS SOFTWARE IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE SOFTWARE, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE SOFTWARE "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE SOFTWARE IS WITH YOU. SHOULD THE SOFTWARE PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR, OR CORRECTION.
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE SOFTWARE AS PERMITTED BY THE ABOVE LICENCE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE SOFTWARE (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE SOFTWARE TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
To install Devel::Kit, copy and paste the appropriate command in to your terminal.
cpanm
cpanm Devel::Kit
CPAN shell
perl -MCPAN -e shell install Devel::Kit
For more information on module installation, please visit the detailed CPAN module installation guide.