1 package Data::Dumper::Concise;
9 use Scalar::Util 'isweak';
11 BEGIN { @ISA = qw(Exporter) }
13 @EXPORT = qw(Dumper DumperF DumperObject);
16 my $dd = Data::Dumper->new([]);
17 $dd->Terse(1)->Indent(1)->Useqq(1)->Deparse(1)->Quotekeys(0)->Sortkeys(1);
21 my $o = Data::Dumper->can('_dump');
22 local *Data::Dumper::_dump = sub {
24 ? 'do { WEAK: ' . $o->(@_) . ' }'
27 DumperObject->Values([ @_ ])->Dump
32 return $code->(map Dumper($_), @_);
37 Data::Dumper::Concise - Less indentation and newlines plus sub deparsing
41 use Data::Dumper::Concise;
49 local $Data::Dumper::Terse = 1;
50 local $Data::Dumper::Indent = 1;
51 local $Data::Dumper::Useqq = 1;
52 local $Data::Dumper::Deparse = 1;
53 local $Data::Dumper::Quotekeys = 0;
54 local $Data::Dumper::Sortkeys = 1;
60 { foo => "bar\nbaz", quux => sub { "fleem" } };
62 Data::Dumper::Concise will give you:
73 instead of the default Data::Dumper output:
76 'quux' => sub { "DUMMY" },
81 (note the tab indentation, oh joy ...)
83 If you need to get the underlying L<Dumper> object just call C<DumperObject>.
85 Also try out C<DumperF> which takes a C<CodeRef> as the first argument to
86 format the output. For example:
88 use Data::Dumper::Concise;
90 warn DumperF { "result: $_[0] result2: $_[1]" } $foo, $bar;
94 warn 'result: ' . Dumper($foo) . ' result2: ' . Dumper($bar);
98 This module always exports a single function, Dumper, which can be called
99 with an array of values to dump those values.
101 It exists, fundamentally, as a convenient way to reproduce a set of Dumper
102 options that we've found ourselves using across large numbers of applications,
103 primarily for debugging output.
105 The principle guiding theme is "all the concision you can get while still
106 having a useful dump and not doing anything cleverer than setting Data::Dumper
107 options" - it's been pointed out to us that Data::Dump::Streamer can produce
108 shorter output with less lines of code. We know. This is simpler and we've
109 never seen it segfault. But for complex/weird structures, it generally rocks.
110 You should use it as well, when Concise is underkill. We do.
112 Why is deparsing on when the aim is concision? Because you often want to know
113 what subroutine refs you have when debugging and because if you were planning
114 to eval this back in you probably wanted to remove subrefs first and add them
115 back in a custom way anyway. Note that this -does- force using the pure perl
116 Dumper rather than the XS one, but I've never in my life seen Data::Dumper
117 show up in a profile so "who cares?".
119 =head1 BUT BUT BUT ...
121 Yes, we know. Consider this module in the ::Tiny spirit and feel free to
122 write a Data::Dumper::Concise::ButWithExtraTwiddlyBits if it makes you
123 happy. Then tell us so we can add it to the see also section.
127 This package also provides:
129 L<Data::Dumper::Concise::Sugar> - provides Dwarn and DwarnS convenience functions
131 L<Devel::Dwarn> - shorter form for Data::Dumper::Concise::Sugar
135 We use for some purposes, and dearly love, the following alternatives:
137 L<Data::Dump> - prettiness oriented but not amazingly configurable
139 L<Data::Dump::Streamer> - brilliant. beautiful. insane. extensive. excessive. try it.
141 L<JSON::XS> - no, really. If it's just plain data, JSON is a great option.
145 mst - Matt S. Trout <mst@shadowcat.co.uk>
149 frew - Arthur Axel "fREW" Schmidt <frioux@gmail.com>
153 Copyright (c) 2010 the Data::Dumper::Concise L</AUTHOR> and L</CONTRIBUTORS>
158 This library is free software and may be distributed under the same terms