Acme-CPANModules-OneLinerTools
view release on metacpan or search on metacpan
lib/Acme/CPANModules/OneLinerTools.pm view on Meta::CPAN
MARKDOWN
entries => [
{
module => 'L',
description => <<'MARKDOWN',
One of the "module autoloader" modules, which happens to have a short name for
one-liner usage. So instead of having to type this:
% perl -MOrg::Parser::Tiny -E'$doc = Org::Parser::Tiny->new->parse_file("/home/budi/todo.org"); ...'
you can now write:
% perl -ML -E'$doc = Org::Parser::Tiny->new->parse_file("/home/budi/todo.org"); ...'
"Module autoloader" modules work using Perl's autoloading mechanism (read
`perlsub` for more details). By declaring a subroutine named `AUTOLOAD` in the
`UNIVERSAL` package, you setup a fallback mechanism when you call an undefined
subroutine. <pm:L>'s AUTOLOADER loads the module using <pm:Module::Load> then
try to invoke the undefined subroutine once again.
MARKDOWN
tags => ['module-loading'],
},
{
module => 'lib::xi',
description => <<'MARKDOWN',
This module can automatically install missing module during run-time using
`cpanm`. Convenient when running a Perl script (that comes without a proper
distribution or `cpanfile`) that uses several modules which you might not have.
The alternative to lib::xi is the "trial and error" method: repeatedly run the
Perl script to see which module it tries and fails to load.
lib::xi works by installing a hook in `@INC`.
MARKDOWN
tags => ['module-loading'],
alternate_modules => [
'Require::Hook::More', # the autoinstalling feature has not been implemented though
],
},
{
module => 'Log::ger::App',
description => <<'MARKDOWN',
A convenient way to display (consume) logs if your application uses
<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"); ...'
you can type:
% perl -MDBIx::Conn::MySQL=mydb -E'$dbh->selectrow_array("query"); ...'
MARKDOWN
tags => ['database', 'dbi'],
},
{
module => 'DBIx::Conn::SQLite',
description => <<'MARKDOWN',
Shortcut when connecting to MySQL database in your one-liner. Instead of:
% perl -MDBI -E'my $dbh = DBI->connect("dbi:SQLite:dbname=mydb", "", ""); $dbh->selectrow_array("query"); ...'
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
=encoding UTF-8
=head1 NAME
Acme::CPANModules::OneLinerTools - List of modules to make your life easier when writing perl one-liners
=head1 VERSION
This document describes version 0.005 of Acme::CPANModules::OneLinerTools (from Perl distribution Acme-CPANModules-OneLinerTools), released on 2024-06-21.
=head1 DESCRIPTION
This list also tries to catalog modules that are meant to be primarily used in
one-liners.
=head1 ACME::CPANMODULES ENTRIES
=over
=item L<L>
Author: L<SONGMU|https://metacpan.org/author/SONGMU>
One of the "module autoloader" modules, which happens to have a short name for
one-liner usage. So instead of having to type this:
% perl -MOrg::Parser::Tiny -E'$doc = Org::Parser::Tiny->new->parse_file("/home/budi/todo.org"); ...'
you can now write:
% perl -ML -E'$doc = Org::Parser::Tiny->new->parse_file("/home/budi/todo.org"); ...'
"Module autoloader" modules work using Perl's autoloading mechanism (read
C<perlsub> for more details). By declaring a subroutine named C<AUTOLOAD> in the
C<UNIVERSAL> package, you setup a fallback mechanism when you call an undefined
subroutine. L<L>'s AUTOLOADER loads the module using L<Module::Load> then
try to invoke the undefined subroutine once again.
=item L<lib::xi>
Author: L<GFUJI|https://metacpan.org/author/GFUJI>
This module can automatically install missing module during run-time using
C<cpanm>. Convenient when running a Perl script (that comes without a proper
distribution or C<cpanfile>) that uses several modules which you might not have.
The alternative to lib::xi is the "trial and error" method: repeatedly run the
Perl script to see which module it tries and fails to load.
lib::xi works by installing a hook in C<@INC>.
Alternate modules: L<Require::Hook::More>
=item L<Log::ger::App>
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>
Author: L<HAARG|https://metacpan.org/author/HAARG>
Forces stack trace when your application warns or dies. Used with the perl's
C<-d> flag:
% perl -d:Confess ...
% perl -d:Confess=dump ...
=item L<Carp::Patch::Config>
Author: L<PERLANCAR|https://metacpan.org/author/PERLANCAR>
L<Carp> is used as a stack trace printer (also indirectly if you use
L<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.
=item L<DBIx::Conn::MySQL>
Author: L<PERLANCAR|https://metacpan.org/author/PERLANCAR>
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"); ...'
you can type:
% perl -MDBIx::Conn::MySQL=mydb -E'$dbh->selectrow_array("query"); ...'
=item L<DBIx::Conn::SQLite>
Author: L<PERLANCAR|https://metacpan.org/author/PERLANCAR>
Shortcut when connecting to MySQL database in your one-liner. Instead of:
% perl -MDBI -E'my $dbh = DBI->connect("dbi:SQLite:dbname=mydb", "", ""); $dbh->selectrow_array("query"); ...'
you can type:
% perl -MDBIx::Conn::SQLite=mydb -E'$dbh->selectrow_array("query"); ...'
=item L<ojo>
Author: L<SRI|https://metacpan.org/author/SRI>
=item L<DDP>
( run in 0.674 second using v1.01-cache-2.11-cpan-39bf76dae61 )