Acme-CPANModules-StructuredDATA
view release on metacpan or search on metacpan
"version" : "0.10"
},
{
"class" : "Dist::Zilla::Plugin::PodnameFromFilename",
"name" : "@Author::PERLANCAR/PodnameFromFilename",
"version" : "0.02"
},
{
"class" : "Dist::Zilla::Plugin::PERLANCAR::EnsurePrereqToSpec",
"config" : {
"Dist::Zilla::Role::ModuleMetadata" : {
"Module::Metadata" : "1.000037",
"version" : "0.006"
}
},
"name" : "@Author::PERLANCAR/PERLANCAR::EnsurePrereqToSpec",
"version" : "0.064"
},
{
"class" : "Dist::Zilla::Plugin::PERLANCAR::MetaResources",
"name" : "@Author::PERLANCAR/PERLANCAR::MetaResources",
"version" : "0.043"
"version" : "0.001"
},
{
"class" : "Dist::Zilla::Plugin::CheckSelfDependency",
"config" : {
"Dist::Zilla::Plugin::CheckSelfDependency" : {
"finder" : [
":InstallModules"
]
},
"Dist::Zilla::Role::ModuleMetadata" : {
"Module::Metadata" : "1.000037",
"version" : "0.006"
}
},
"name" : "@Author::PERLANCAR/CheckSelfDependency",
"version" : "0.011"
},
{
"class" : "Dist::Zilla::Plugin::Git::Contributors",
"config" : {
"Dist::Zilla::Plugin::Git::Contributors" : {
}
],
"include_underscores" : 0
},
"Dist::Zilla::Role::MetaProvider::Provider" : {
"$Dist::Zilla::Role::MetaProvider::Provider::VERSION" : "2.002004",
"inherit_missing" : 1,
"inherit_version" : 1,
"meta_noindex" : 1
},
"Dist::Zilla::Role::ModuleMetadata" : {
"Module::Metadata" : "1.000037",
"version" : "0.006"
}
},
"name" : "@Author::PERLANCAR/MetaProvides::Package",
"version" : "2.004003"
},
{
"class" : "Dist::Zilla::Plugin::PERLANCAR::Authority",
"name" : "@Author::PERLANCAR/PERLANCAR::Authority",
"version" : "0.001"
class: Dist::Zilla::Plugin::Rinci::AbstractFromMeta
name: '@Author::PERLANCAR/Rinci::AbstractFromMeta'
version: '0.10'
-
class: Dist::Zilla::Plugin::PodnameFromFilename
name: '@Author::PERLANCAR/PodnameFromFilename'
version: '0.02'
-
class: Dist::Zilla::Plugin::PERLANCAR::EnsurePrereqToSpec
config:
Dist::Zilla::Role::ModuleMetadata:
Module::Metadata: '1.000037'
version: '0.006'
name: '@Author::PERLANCAR/PERLANCAR::EnsurePrereqToSpec'
version: '0.064'
-
class: Dist::Zilla::Plugin::PERLANCAR::MetaResources
name: '@Author::PERLANCAR/PERLANCAR::MetaResources'
version: '0.043'
-
class: Dist::Zilla::Plugin::CheckChangeLog
name: '@Author::PERLANCAR/CheckChangeLog'
-
class: Dist::Zilla::Plugin::CheckMetaResources
name: '@Author::PERLANCAR/CheckMetaResources'
version: '0.001'
-
class: Dist::Zilla::Plugin::CheckSelfDependency
config:
Dist::Zilla::Plugin::CheckSelfDependency:
finder:
- ':InstallModules'
Dist::Zilla::Role::ModuleMetadata:
Module::Metadata: '1.000037'
version: '0.006'
name: '@Author::PERLANCAR/CheckSelfDependency'
version: '0.011'
-
class: Dist::Zilla::Plugin::Git::Contributors
config:
Dist::Zilla::Plugin::Git::Contributors:
git_version: 2.25.1
include_authors: 0
include_releaser: 1
-
class: Dist::Zilla::Plugin::FinderCode
name: '@Author::PERLANCAR/MetaProvides::Package/AUTOVIV/:InstallModulesPM'
version: '6.024'
include_underscores: 0
Dist::Zilla::Role::MetaProvider::Provider:
$Dist::Zilla::Role::MetaProvider::Provider::VERSION: '2.002004'
inherit_missing: '1'
inherit_version: '1'
meta_noindex: '1'
Dist::Zilla::Role::ModuleMetadata:
Module::Metadata: '1.000037'
version: '0.006'
name: '@Author::PERLANCAR/MetaProvides::Package'
version: '2.004003'
-
class: Dist::Zilla::Plugin::PERLANCAR::Authority
name: '@Author::PERLANCAR/PERLANCAR::Authority'
version: '0.001'
-
class: Dist::Zilla::Plugin::OurDate
name: '@Author::PERLANCAR/OurDate'
structure to DATA
VERSION
This document describes version 0.002 of
Acme::CPANModules::StructuredDATA (from Perl distribution
Acme-CPANModules-StructuredDATA), released on 2022-03-18.
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
part2,14,17,important
This is part1
This is part
two
The first paragraph after DATA is called the TOC which lists all the
parts along with their offsets and lengths. It is therefore possible
to locate any part just from reading the TOC instead of scanning for
headers on the whole data. It is useful when the amount of data is
quite large and you need quick access to random parts.
* Inline::Files - Multiple virtual files at the end of your code
Author: AMBS <https://metacpan.org/author/AMBS>
This is a prior art for Data::Section but more magical (using source
filters) and allows writing in addition to reading your parts. It
completely replaces DATA with an unlimited number of LABEL's. I'd be
wary in using it, and the module itself gives such warning.
lib/Acme/CPANModules/StructuredDATA.pm view on Meta::CPAN
our $DATE = '2022-03-18'; # DATE
our $DIST = 'Acme-CPANModules-StructuredDATA'; # DIST
our $VERSION = '0.002'; # VERSION
our $LIST = {
summary => 'List of modules that give some structure to DATA',
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.
_
entries => [
{
module=>'Data::Section',
description => <<'_',
lib/Acme/CPANModules/StructuredDATA.pm view on Meta::CPAN
part1,0,14
part2,14,17,important
This is part1
This is part
two
The first paragraph after __DATA__ is called the TOC which lists all the parts
along with their offsets and lengths. It is therefore possible to locate any
part just from reading the TOC instead of scanning for headers on the whole
data. It is useful when the amount of data is quite large and you need quick
access to random parts.
_
},
{
module=>'Inline::Files',
description => <<'_',
This is a prior art for <pm:Data::Section> but more magical (using source
filters) and allows writing in addition to reading your parts. It completely
lib/Acme/CPANModules/StructuredDATA.pm view on Meta::CPAN
Acme::CPANModules::StructuredDATA - List of modules that give some structure to DATA
=head1 VERSION
This document describes version 0.002 of Acme::CPANModules::StructuredDATA (from Perl distribution Acme-CPANModules-StructuredDATA), released on 2022-03-18.
=head1 DESCRIPTION
The DATA file handle is a convenient feature provided by Perl to let scripts
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
part2,14,17,important
This is part1
This is part
two
The first paragraph after B<DATA> is called the TOC which lists all the parts
along with their offsets and lengths. It is therefore possible to locate any
part just from reading the TOC instead of scanning for headers on the whole
data. It is useful when the amount of data is quite large and you need quick
access to random parts.
=item * L<Inline::Files> - Multiple virtual files at the end of your code
Author: L<AMBS|https://metacpan.org/author/AMBS>
This is a prior art for L<Data::Section> but more magical (using source
filters) and allows writing in addition to reading your parts. It completely
replaces B<DATA> with an unlimited number of B<LABEL>'s. I'd be wary in using
( run in 0.596 second using v1.01-cache-2.11-cpan-5dc5da66d9d )