Acme-CPANModules-DumpingDataForDebugging

 view release on metacpan or  search on metacpan

META.json  view on Meta::CPAN

1
2
3
4
5
6
7
8
9
10
11
12
{
   "abstract" : "List of modules and tips when dumping data structures for debugging",
   "author" : [
      "perlancar <perlancar@cpan.org>"
   ],
   "dynamic_config" : 0,
   "generated_by" : "Dist::Zilla version 6.030, CPAN::Meta::Converter version 2.150010",
   "license" : [
      "perl_5"
   ],
   "meta-spec" : {

META.json  view on Meta::CPAN

199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
   "version" : "0.10"
},
{
   "class" : "Dist::Zilla::Plugin::PodnameFromFilename",
   "name" : "@Author::PERLANCAR/PodnameFromFilename",
   "version" : "0.02"
},
{
   "class" : "Dist::Zilla::Plugin::PERLANCAR::EnsurePrereqToSpec",
   "config" : {
      "Dist::Zilla::Role::ModuleMetadata" : {
         "Module::Metadata" : "1.000037",
         "version" : "0.006"
      }
   },
   "name" : "@Author::PERLANCAR/PERLANCAR::EnsurePrereqToSpec",
   "version" : "0.064"
},
{
   "class" : "Dist::Zilla::Plugin::PERLANCAR::MetaResources",
   "name" : "@Author::PERLANCAR/PERLANCAR::MetaResources",
   "version" : "0.043"

META.json  view on Meta::CPAN

230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
   "version" : "0.001"
},
{
   "class" : "Dist::Zilla::Plugin::CheckSelfDependency",
   "config" : {
      "Dist::Zilla::Plugin::CheckSelfDependency" : {
         "finder" : [
            ":InstallModules"
         ]
      },
      "Dist::Zilla::Role::ModuleMetadata" : {
         "Module::Metadata" : "1.000037",
         "version" : "0.006"
      }
   },
   "name" : "@Author::PERLANCAR/CheckSelfDependency",
   "version" : "0.011"
},
{
   "class" : "Dist::Zilla::Plugin::Git::Contributors",
   "config" : {
      "Dist::Zilla::Plugin::Git::Contributors" : {

META.json  view on Meta::CPAN

291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
            }
         ],
         "include_underscores" : 0
      },
      "Dist::Zilla::Role::MetaProvider::Provider" : {
         "$Dist::Zilla::Role::MetaProvider::Provider::VERSION" : "2.002004",
         "inherit_missing" : 1,
         "inherit_version" : 1,
         "meta_noindex" : 1
      },
      "Dist::Zilla::Role::ModuleMetadata" : {
         "Module::Metadata" : "1.000037",
         "version" : "0.006"
      }
   },
   "name" : "@Author::PERLANCAR/MetaProvides::Package",
   "version" : "2.004003"
},
{
   "class" : "Dist::Zilla::Plugin::PERLANCAR::Authority",
   "name" : "@Author::PERLANCAR/PERLANCAR::Authority",
   "version" : "0.001"

META.yml  view on Meta::CPAN

1
2
3
4
5
6
7
8
9
10
11
12
---
abstract: 'List of modules and tips when dumping data structures for debugging'
author:
  - 'perlancar <perlancar@cpan.org>'
build_requires:
  File::Spec: '0'
  IO::Handle: '0'
  IPC::Open3: '0'
  Test::More: '0'
configure_requires:
  ExtUtils::MakeMaker: '0'
dynamic_config: 0

META.yml  view on Meta::CPAN

115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
  class: Dist::Zilla::Plugin::Rinci::AbstractFromMeta
  name: '@Author::PERLANCAR/Rinci::AbstractFromMeta'
  version: '0.10'
-
  class: Dist::Zilla::Plugin::PodnameFromFilename
  name: '@Author::PERLANCAR/PodnameFromFilename'
  version: '0.02'
-
  class: Dist::Zilla::Plugin::PERLANCAR::EnsurePrereqToSpec
  config:
    Dist::Zilla::Role::ModuleMetadata:
      Module::Metadata: '1.000037'
      version: '0.006'
  name: '@Author::PERLANCAR/PERLANCAR::EnsurePrereqToSpec'
  version: '0.064'
-
  class: Dist::Zilla::Plugin::PERLANCAR::MetaResources
  name: '@Author::PERLANCAR/PERLANCAR::MetaResources'
  version: '0.043'
-
  class: Dist::Zilla::Plugin::CheckChangeLog
  name: '@Author::PERLANCAR/CheckChangeLog'

META.yml  view on Meta::CPAN

138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
-
  class: Dist::Zilla::Plugin::CheckMetaResources
  name: '@Author::PERLANCAR/CheckMetaResources'
  version: '0.001'
-
  class: Dist::Zilla::Plugin::CheckSelfDependency
  config:
    Dist::Zilla::Plugin::CheckSelfDependency:
      finder:
        - ':InstallModules'
    Dist::Zilla::Role::ModuleMetadata:
      Module::Metadata: '1.000037'
      version: '0.006'
  name: '@Author::PERLANCAR/CheckSelfDependency'
  version: '0.011'
-
  class: Dist::Zilla::Plugin::Git::Contributors
  config:
    Dist::Zilla::Plugin::Git::Contributors:
      git_version: 2.25.1
      include_authors: 0
      include_releaser: 1

META.yml  view on Meta::CPAN

185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
        -
          class: Dist::Zilla::Plugin::FinderCode
          name: '@Author::PERLANCAR/MetaProvides::Package/AUTOVIV/:InstallModulesPM'
          version: '6.030'
      include_underscores: 0
    Dist::Zilla::Role::MetaProvider::Provider:
      $Dist::Zilla::Role::MetaProvider::Provider::VERSION: '2.002004'
      inherit_missing: 1
      inherit_version: 1
      meta_noindex: 1
    Dist::Zilla::Role::ModuleMetadata:
      Module::Metadata: '1.000037'
      version: '0.006'
  name: '@Author::PERLANCAR/MetaProvides::Package'
  version: '2.004003'
-
  class: Dist::Zilla::Plugin::PERLANCAR::Authority
  name: '@Author::PERLANCAR/PERLANCAR::Authority'
  version: '0.001'
-
  class: Dist::Zilla::Plugin::OurDate
  name: '@Author::PERLANCAR/OurDate'

Makefile.PL  view on Meta::CPAN

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
# This file was automatically generated by Dist::Zilla::Plugin::MakeMaker v6.030.
use strict;
 
 
 
 
my %WriteMakefileArgs = (
  "ABSTRACT" => "List of modules and tips when dumping data structures for debugging",
  "AUTHOR" => "perlancar <perlancar\@cpan.org>",
  "CONFIGURE_REQUIRES" => {
    "ExtUtils::MakeMaker" => 0
  },
  "DISTNAME" => "Acme-CPANModules-DumpingDataForDebugging",
  "LICENSE" => "perl",
  "NAME" => "Acme::CPANModules::DumpingDataForDebugging",
  "PREREQ_PM" => {
    "strict" => 0
  },

README  view on Meta::CPAN

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
NAME
    Acme::CPANModules::DumpingDataForDebugging - List of modules and tips
    when dumping data structures for debugging
 
VERSION
    This document describes version 0.002 of
    Acme::CPANModules::DumpingDataForDebugging (from Perl distribution
    Acme-CPANModules-DumpingDataForDebugging), released on 2023-10-29.
 
DESCRIPTION
    This list catalogs some of the modules you can you to dump your data
    structures for debugging purposes, so the modules will be judged mostly
    by the appropriateness of its output for human viewing (instead of other
    criteria like speed, footprint, etc).
 
ACME::CPANMODULES ENTRIES
    Data::Dumper
        Author: NWCLARK <https://metacpan.org/author/NWCLARK>
 
        Everybody knows this module and it's core so sometimes it's the only
        appropriate choice. However, the default setting is not really
        optimized for viewing by human. I suggest you tweak these before
        dumping your data:
 
        *   Set $Data::Dumper::Useqq to 1.
 
        By default, Data::Dumper quotes strings using single-quotes and does
        not quote things like "\n" and "\b" making it difficult to spot
        special characters.
 
    Data::Dump
        Author: GARU <https://metacpan.org/author/GARU>
 
        A data dumper that produces nicer Perl code output, with features
        like vertical alignment of "=>" when dumping hashes, compacting
        sequences like 1,2,3,4,5,6 to 1..6, compacting repeating characters
        in string like "ccccccccccccccccccccc" to ("c" x 21), and so on.
 
        It tries harder to produce Perl code that generates the original
        data structure, particularly with circular references. But with
        interlinked references like trees, Data::Dumper might be more
        helpful in showing you which references get mentioned where. For
        example this data:
 
         $tree = {children=>[{children=>[{}]}, {children=>[]}]};
         $tree->{children}[0]{parent}=$tree;
         $tree->{children}[1]{parent}=$tree;
         $tree->{children}[0]{children}[0]{parent} = $tree->{children}[0];
 
        Data::Dump will produce:
 
         do {
            my $a = {

README  view on Meta::CPAN

116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
        inheritance information. It's also very customizable. It uses its
        own format though, and my preference for dumping is the Perl format
        (with additional informations/hints as comments) so I've never used
        it in my daily coding activities. I probably should though.
 
    JSON::Color
        Author: PERLANCAR <https://metacpan.org/author/PERLANCAR>
 
        JSON is a limited format; it cannot represent many things that Perl
        supports e.g. globs, circular references, or even ASCII NUL. But if
        you are working only with JSON-able data, this JSON dumping module
        adds color output.
 
    YAML::Tiny::Color
        Author: SHARYANTO <https://metacpan.org/author/SHARYANTO>
 
FAQ
  What is an Acme::CPANModules::* module?
    An Acme::CPANModules::* module, like this module, contains just a list
    of module names that share a common characteristics. It is a way to
    categorize modules and document CPAN. See Acme::CPANModules for more

lib/Acme/CPANModules/DumpingDataForDebugging.pm  view on Meta::CPAN

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
 
use strict;
 
our $AUTHORITY = 'cpan:PERLANCAR'; # AUTHORITY
our $DATE = '2023-10-29'; # DATE
our $DIST = 'Acme-CPANModules-DumpingDataForDebugging'; # DIST
our $VERSION = '0.002'; # VERSION
 
our $LIST = {
    summary => 'List of modules and tips when dumping data structures for debugging',
    description => <<'_',
 
This list catalogs some of the modules you can you to dump your data structures
for debugging purposes, so the modules will be judged mostly by the
appropriateness of its output for human viewing (instead of other criteria like
speed, footprint, etc).
 
_
    entries => [
        {
            module=>'Data::Dumper',
            tags => ['perl'],
            description => <<'_',
 
Everybody knows this module and it's core so sometimes it's the only appropriate
choice. However, the default setting is not really optimized for viewing by
human. I suggest you tweak these before dumping your data:
 
* Set $Data::Dumper::Useqq to 1.
 
By default, <pm:Data::Dumper> quotes strings using single-quotes and does not
quote things like "\n" and "\b" making it difficult to spot special characters.
 
 
_
        },
 
        {
            module=>'Data::Dump',
            tags => ['perl'],
            description => <<'_',
 
A data dumper that produces nicer Perl code output, with features like vertical
alignment of "=>" when dumping hashes, compacting sequences like 1,2,3,4,5,6 to
1..6, compacting repeating characters in string like "ccccccccccccccccccccc" to
("c" x 21), and so on.
 
It tries harder to produce Perl code that generates the original data structure,
particularly with circular references. But with interlinked references like
trees, Data::Dumper might be more helpful in showing you which references get
mentioned where. For example this data:
 
    $tree = {children=>[{children=>[{}]}, {children=>[]}]};
    $tree->{children}[0]{parent}=$tree;
    $tree->{children}[1]{parent}=$tree;
    $tree->{children}[0]{children}[0]{parent} = $tree->{children}[0];
 
Data::Dump will produce:
 
    do {
       my $a = {

lib/Acme/CPANModules/DumpingDataForDebugging.pm  view on Meta::CPAN

147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
_
        },
 
        {
            module=>'JSON::Color',
            tags => ['json'],
            description => <<'_',
 
JSON is a limited format; it cannot represent many things that Perl supports
e.g. globs, circular references, or even ASCII NUL. But if you are working only
with JSON-able data, this JSON dumping module adds color output.
 
_
        },
 
        {
            module=>'YAML::Tiny::Color',
            tags => ['yaml'],
            description => <<'_',
 
_
        },
    ],
};
 
1;
# ABSTRACT: List of modules and tips when dumping data structures for debugging
 
__END__
 
=pod
 
=encoding UTF-8
 
=head1 NAME
 
Acme::CPANModules::DumpingDataForDebugging - List of modules and tips when dumping data structures for debugging
 
=head1 VERSION
 
This document describes version 0.002 of Acme::CPANModules::DumpingDataForDebugging (from Perl distribution Acme-CPANModules-DumpingDataForDebugging), released on 2023-10-29.
 
=head1 DESCRIPTION
 
This list catalogs some of the modules you can you to dump your data structures
for debugging purposes, so the modules will be judged mostly by the
appropriateness of its output for human viewing (instead of other criteria like
speed, footprint, etc).
 
=head1 ACME::CPANMODULES ENTRIES
 
=over
 
=item L<Data::Dumper>
 
 
Everybody knows this module and it's core so sometimes it's the only appropriate
choice. However, the default setting is not really optimized for viewing by
human. I suggest you tweak these before dumping your data:
 
=over
 
=item * Set $Data::Dumper::Useqq to 1.
 
=back
 
By default, L<Data::Dumper> quotes strings using single-quotes and does not
quote things like "\n" and "\b" making it difficult to spot special characters.
 
 
=item L<Data::Dump>
 
 
A data dumper that produces nicer Perl code output, with features like vertical
alignment of "=>" when dumping hashes, compacting sequences like 1,2,3,4,5,6 to
1..6, compacting repeating characters in string like "ccccccccccccccccccccc" to
("c" x 21), and so on.
 
It tries harder to produce Perl code that generates the original data structure,
particularly with circular references. But with interlinked references like
trees, Data::Dumper might be more helpful in showing you which references get
mentioned where. For example this data:
 
 $tree = {children=>[{children=>[{}]}, {children=>[]}]};
 $tree->{children}[0]{parent}=$tree;
 $tree->{children}[1]{parent}=$tree;
 $tree->{children}[0]{children}[0]{parent} = $tree->{children}[0];
 
Data::Dump will produce:
 
 do {
    my $a = {

lib/Acme/CPANModules/DumpingDataForDebugging.pm  view on Meta::CPAN

310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
dumping is the Perl format (with additional informations/hints as comments) so
I've never used it in my daily coding activities. I probably should though.
 
 
=item L<JSON::Color>
 
 
JSON is a limited format; it cannot represent many things that Perl supports
e.g. globs, circular references, or even ASCII NUL. But if you are working only
with JSON-able data, this JSON dumping module adds color output.
 
 
=item L<YAML::Tiny::Color>
 
 
=back
 
=head1 FAQ



( run in 0.928 second using v1.01-cache-2.11-cpan-49f99fa48dc )