view release on metacpan or  search on metacpan

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

package Acme::CPANModules::DumpingDataForDebugging;

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 = {
         children => [
          { children => [{ parent => 'fix' }], parent => 'fix' },
          { children => [], parent => 'fix' },
        ],
      };
      $a->{children}[0]{children}[0]{parent} = $a->{children}[0];
      $a->{children}[0]{parent} = $a;
      $a->{children}[1]{parent} = $a;
      $a;
    }

while Data::Dumper will produce:

    $VAR1 = {
              'children' => [
                              {
                                'children' => [
                                                {
                                                  'parent' => $VAR1->{'children'}[0]
                                                }
                                              ],
                                'parent' => $VAR1
                              },
                              {
                                'parent' => $VAR1,

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

I've never used it in my daily coding activities. I probably should though.

_
        },

        {
            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>

Author: L<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:

=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>

Author: L<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 = {
      children => [
       { children => [{ parent => 'fix' }], parent => 'fix' },
       { children => [], parent => 'fix' },
     ],
   };
   $a->{children}[0]{children}[0]{parent} = $a->{children}[0];
   $a->{children}[0]{parent} = $a;
   $a->{children}[1]{parent} = $a;
   $a;
 }

while Data::Dumper will produce:

 $VAR1 = {
           'children' => [
                           {
                             'children' => [
                                             {
                                               'parent' => $VAR1->{'children'}[0]
                                             }
                                           ],
                             'parent' => $VAR1
                           },
                           {
                             'parent' => $VAR1,