view release on metacpan or  search on metacpan

README  view on Meta::CPAN

DESCRIPTION
    The DATA file handle is a convenient feature provided by Perl to let
    scripts access its own source code (specifically the part after END or
    DATA). Scripts can usually put some data so they can run without
    additional data files.

    Instead of just a stream of bytes, some modules allow you to access the
    DATA as some kind of structured storage.

ACME::CPANMODULES ENTRIES
    *   Data::Section - read multiple hunks of data out of your DATA section

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

        With this module, you can put several strings in your DATA section,
        each prepended with a header line containing the label for each. For
        example:

         __[ content1 ]__
         content for content1.
 
         __[ content2 ]__
         content
         for
         content2

        and access each string by referring to its label.

    *   Data::Section::Seekable - Read and write parts from data section

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

        This module is similar to Data::Section in letting you put several
        multipart content in DATA with the exception that it writes a table
        of content (TOC) of all parts at the beginning of DATA, e.g.:

         __DATA__
         Data::Section::Seekable v1
         part1,0,14

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

Instead of just a stream of bytes, some modules allow you to access the DATA as
some kind of structured storage.

_
    entries => [
        {
            module=>'Data::Section',
            description => <<'_',

With this module, you can put several strings in your DATA section, each
prepended with a header line containing the label for each. For example:

    __[ content1 ]__
    content for content1.

    __[ content2 ]__
    content
    for
    content2

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

access its own source code (specifically the part after B<END> or B<DATA>).
Scripts can usually put some data so they can run without additional data files.

Instead of just a stream of bytes, some modules allow you to access the DATA as
some kind of structured storage.

=head1 ACME::CPANMODULES ENTRIES

=over

=item * L<Data::Section> - read multiple hunks of data out of your DATA section

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

With this module, you can put several strings in your DATA section, each
prepended with a header line containing the label for each. For example:

 __[ content1 ]__
 content for content1.
 
 __[ content2 ]__
 content
 for
 content2

and access each string by referring to its label.


=item * L<Data::Section::Seekable> - Read and write parts from data section

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

This module is similar to L<Data::Section> in letting you put several
multipart content in DATA with the exception that it writes a table of content
(TOC) of all parts at the beginning of DATA, e.g.:

 __DATA__
 Data::Section::Seekable v1
 part1,0,14