import p5-Data-Dumper-Concise, from Andrew Fresh, ok landry@
This module always exports a single function, Dumper, which can be
called with an array of values to dump those values.
It exists, fundamentally, as a convenient way to reproduce a set
of Dumper options that we've found ourselves using across large
numbers of applications, primarily for debugging output.
The principle guiding theme is "all the concision you can get while
still having a useful dump and not doing anything cleverer than
setting Data::Dumper options" - it's been pointed out to us that
Data::Dump::Streamer can produce shorter output with less lines of
code. We know. This is simpler and we've never seen it segfault.
But for complex/weird structures, it generally rocks. You should
use it as well, when Concise is underkill. We do.
Why is deparsing on when the aim is concision? Because you often
want to know what subroutine refs you have when debugging and because
if you were planning to eval this back in you probably wanted to
remove subrefs first and add them back in a custom way anyway. Note
that this -does- force using the pure perl Dumper rather than the
XS one, but I've never in my life seen Data::Dumper show up in a
profile so "who cares?".
2012-04-06 05:25:08 -04:00
|
|
|
MD5 (Data-Dumper-Concise-2.020.tar.gz) = jig1oTBNaAFw5IMJOzMLcA==
|
|
|
|
|
RMD160 (Data-Dumper-Concise-2.020.tar.gz) = kkADhqt9CGM03TJiwghcOYAnABE=
|
|
|
|
|
SHA1 (Data-Dumper-Concise-2.020.tar.gz) = m9F2Fry5cl/ibxvoOyVWbqJj+lI=
|
|
|
|
|
SHA256 (Data-Dumper-Concise-2.020.tar.gz) = Fp45pnysY36SY6sxz6EpsKx7uYGP8epsA/TWJppIZ30=
|
|
|
|
|
SIZE (Data-Dumper-Concise-2.020.tar.gz) = 21771
|