Acme-CPANModules-KitchenSinks

 view release on metacpan or  search on metacpan

README  view on Meta::CPAN


DESCRIPTION
    A "kitchen sink" module is a module that tries to provide all sorts of
    functions/methods for various things. It often starts as a developer's
    personal "general utilities" library that grows and grows to the point
    of "it should probably be refactored into multiple modules (but isn't
    yet)". Often it also contains functionalities that are already present
    in other modules, but added into the module anyway because it is
    convenient for the developer.

    This list catalogs modules that I think are kitchen sink libraries.

ACME::CPANMODULES ENTRIES
    *   Data::Table::Text

        Author: PRBRENAN <https://metacpan.org/author/PRBRENAN>

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

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

    summary => 'List of kitchen sink libraries',
    description => <<'_',

A "kitchen sink" module is a module that tries to provide all sorts of
functions/methods for various things. It often starts as a developer's personal
"general utilities" library that grows and grows to the point of "it should
probably be refactored into multiple modules (but isn't yet)". Often it also
contains functionalities that are already present in other modules, but added
into the module anyway because it is convenient for the developer.

This list catalogs modules that I think are kitchen sink libraries.

_
    entries => [
        {module=>'Data::Table::Text'},
    ],
};

1;
# ABSTRACT: List of kitchen sink libraries

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


=head1 DESCRIPTION

A "kitchen sink" module is a module that tries to provide all sorts of
functions/methods for various things. It often starts as a developer's personal
"general utilities" library that grows and grows to the point of "it should
probably be refactored into multiple modules (but isn't yet)". Often it also
contains functionalities that are already present in other modules, but added
into the module anyway because it is convenient for the developer.

This list catalogs modules that I think are kitchen sink libraries.

=head1 ACME::CPANMODULES ENTRIES

=over

=item * L<Data::Table::Text>

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

=back



( run in 0.230 second using v1.01-cache-2.11-cpan-4d50c553e7e )