Acme-CPANModules-OneLinerTools

 view release on metacpan or  search on metacpan

README  view on Meta::CPAN

    Log::ger::App
        Author: PERLANCAR <https://metacpan.org/author/PERLANCAR>

        A convenient way to display (consume) logs if your application uses
        Log::ger to produce logs.

    DD::Dummy
        Author: PERLANCAR <https://metacpan.org/author/PERLANCAR>

        My preference when dumping data structure when debugging Perl
        application is, well, Perl format (unlike some others which prefer
        custom format like Data::Printer). The DD-Dummy distribution
        provides DD module, which in turn exports "dd" to dump your data
        structures for debugging using Data::Dump. Another good alternative
        is XXX which by default uses YAML output but can be changed with
        this environment variable setting:

         PERL_XXX_DUMPER=Data::Dump

        Alternate modules: XXX, Data::Printer

    Devel::Confess
        Author: HAARG <https://metacpan.org/author/HAARG>

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

<pm:Log::ger> to produce logs.

MARKDOWN
            tags => ['logging'],
        },

        {
            module => 'DD::Dummy',
            description => <<'MARKDOWN',

My preference when dumping data structure when debugging Perl application is,
well, Perl format (unlike some others which prefer custom format like
<pm:Data::Printer>). The DD-Dummy distribution provides <pm:DD> module, which in
turn exports `dd` to dump your data structures for debugging using
<pm:Data::Dump>. Another good alternative is <pm:XXX> which by default uses YAML
output but can be changed with this environment variable setting:

    PERL_XXX_DUMPER=Data::Dump

MARKDOWN
            alternate_modules => ['XXX', 'Data::Printer'],
            tags => ['debugging'],
        },

        {
            module => 'Devel::Confess',
            description => <<'MARKDOWN',

Forces stack trace when your application warns or dies. Used with the perl's
`-d` flag:

    % perl -d:Confess ...
    % perl -d:Confess=dump ...

MARKDOWN
            tags => ['debugging'],
        },

        {
            module => 'Carp::Patch::Config',
            description => <<'MARKDOWN',

<pm:Carp> is used as a stack trace printer (also indirectly if you use
<pm:Devel::Confess>). Sometimes you want to customize some Carp parameters like
$Carp::MaxArgNums and $Carp::MaxArgLen from the command-line, and this is where
this module helps.

MARKDOWN
            tags => ['debugging'],
        },

        {
            module => 'DBIx::Conn::MySQL',
            description => <<'MARKDOWN',

Shortcut when connecting to MySQL database in your one-liner. Instead of:

    % perl -MDBI -E'my $dbh = DBI->connect("dbi:mysql:database=mydb", "someuser", "somepass"); $dbh->selectrow_array("query"); ...'

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

you can type:

    % perl -MDBIx::Conn::SQLite=mydb -E'$dbh->selectrow_array("query"); ...'

MARKDOWN
            tags => ['database', 'dbi'],
        },

        {module=>'ojo'},
        {module=>'DDP', summary=>'From the Data::Printer distribution', tags=>['debugging']},
        {module=>'XXX', tags=>['debugging']},
        {module=>'eval', tags=>['debugging']},
        {module=>'this_mod', tags=>['module-loading']},
        {module=>'lib::filter', tags=>['debugging', 'module-loading']},
    ],
};

1;
# ABSTRACT: List of modules to make your life easier when writing perl one-liners

__END__

=pod

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

Author: L<PERLANCAR|https://metacpan.org/author/PERLANCAR>

A convenient way to display (consume) logs if your application uses
L<Log::ger> to produce logs.


=item L<DD::Dummy>

Author: L<PERLANCAR|https://metacpan.org/author/PERLANCAR>

My preference when dumping data structure when debugging Perl application is,
well, Perl format (unlike some others which prefer custom format like
L<Data::Printer>). The DD-Dummy distribution provides L<DD> module, which in
turn exports C<dd> to dump your data structures for debugging using
L<Data::Dump>. Another good alternative is L<XXX> which by default uses YAML
output but can be changed with this environment variable setting:

 PERL_XXX_DUMPER=Data::Dump


Alternate modules: L<XXX>, L<Data::Printer>

=item L<Devel::Confess>