App-DataPackUtils
view release on metacpan or search on metacpan
script/datapack-modules view on Meta::CPAN
[--nostripper-ws] [-o=s] [--output=s] [--overwrite]
[--page-result[=program]] [--postamble=s] [--preamble=s]
[--put-hook-at-the-end] [--stripper] [--stripper-comment]
[--stripper-log] [--stripper-maintain-linum] [--stripper-pod]
[--stripper-ws] [module_name] ...
Examples:
Datapack two modules:
% datapack-modules Text::Table::Tiny Try::Tiny
=head1 DESCRIPTION
Both this module and C<Module:FatPack> generate source code that embeds modules'
source codes and load them on-demand via require hook. The difference is that
the modules' source codes are put in C<__DATA__> section instead of regular Perl
hashes (fatpack uses C<%fatpacked>). This reduces compilation overhead, although
this is not noticeable unless when the number of embedded modules is quite
large. For example, in C<App::pause>, the C<pause> script embeds ~320 modules with
a total of ~54000 lines. The overhead of fatpack code is ~49ms on my PC, while
( run in 0.707 second using v1.01-cache-2.11-cpan-05444aca049 )