view release on metacpan or search on metacpan
0.02 2016-02-21 (PERLANCAR)
- Remove file lib/Acme/CPANLists/Import/NEILB/Retired.pm that
accidentally got copied.
0.01 2016-02-20 (PERLANCAR)
- First release.
view release on metacpan or search on metacpan
lib/Acme/CPANLists/Import/PERLANCAR/GetoptModules.pm view on Meta::CPAN
package Acme::CPANLists::Import::PERLANCAR::GetoptModules;
our $DATE = '2016-12-26'; # DATE
our $VERSION = '0.001'; # VERSION
our @Module_Lists = ({description=>"This list is generated by extracting module names mentioned in [https://perlancar.wordpress.com/2016/12/02/getopt-modules-02-getoptstd/] (retrieved on 2016-12-26). Visit the URL for the full contents.",entries=>[{m...
1;
# ABSTRACT: Modules mentioned in PERLANCAR's mini-article series on Getopt modules (2016)
__END__
lib/Acme/CPANLists/Import/PERLANCAR/GetoptModules.pm view on Meta::CPAN
=item * L<Opt::Imistic>
=item * L<overload>
=item * L<Getopt::Lucid>
=item * L<Getopt::Std::Strict>
=item * L<Getopt::Declare>
view release on metacpan or search on metacpan
lib/Acme/CPANModules/BPOM/FoodRegistration.pm view on Meta::CPAN
From <pm:App::MineralUtils>: <prog:convert-magnesium-unit>,
<prog:convert-potassium-unit>, <prog:convert-sodium-unit>.
From <pm:App::VitaminUtils>: <prog:convert-choline-unit>,
<prog:convert-cobalamin-unit>, <prog:convert-pantothenic-acid-unit>,
<prog:convert-pyridoxine-unit>, <prog:convert-vitamin-a-unit>,
<prog:convert-vitamin-b12-unit>, <prog:convert-vitamin-b5-unit>,
<prog:convert-vitamin-b6-unit>, <prog:convert-vitamin-d-unit>,
<prog:convert-vitamin-e-unit>.
lib/Acme/CPANModules/BPOM/FoodRegistration.pm view on Meta::CPAN
From L<App::MineralUtils>: L<convert-magnesium-unit>,
L<convert-potassium-unit>, L<convert-sodium-unit>.
From L<App::VitaminUtils>: L<convert-choline-unit>,
L<convert-cobalamin-unit>, L<convert-pantothenic-acid-unit>,
L<convert-pyridoxine-unit>, L<convert-vitamin-a-unit>,
L<convert-vitamin-b12-unit>, L<convert-vitamin-b5-unit>,
L<convert-vitamin-b6-unit>, L<convert-vitamin-d-unit>,
L<convert-vitamin-e-unit>.
view release on metacpan or search on metacpan
lib/Acme/CPANModules_ScenarioR/CalculatingDayOfWeek.pm view on Meta::CPAN
## no critic
package Acme::CPANModules_ScenarioR::CalculatingDayOfWeek;
our $VERSION = 0.002; # VERSION
our $results = [[200,"OK",[{_name=>"participant=DateTime",_succinct_name=>"D",errors=>3.8e-08,participant=>"DateTime",pct_faster_vs_slowest=>0,pct_slower_vs_fastest=>80.570996978852,rate=>37000,samples=>24,time=>27},{_name=>"participant=Date::DayOfWe...
1;
# ABSTRACT: List of modules to calculate day of week
=head1 DESCRIPTION
view release on metacpan or search on metacpan
lib/Acme/CPANModules/FormattingDate.pm view on Meta::CPAN
verbose date component key names and inconsistent usage of plurals, to having to
use a separate method to "create the formatter" first.
**PHP**
PHP decided to invent its own date template format. Its `date()` function
accepts template string in which you specify single letter conversions like `Y'
(for 4-digit year), `y` (2-digit year), and so on. Some of the letters mean the
same like their counterpart in strftime, but some are different (examples: `i`,
`a`, `M`, and so on). The use of single letter means it's more concise, but the
format becomes unsuitable if you want to put other stuffs (like some string
lib/Acme/CPANModules/FormattingDate.pm view on Meta::CPAN
verbose date component key names and inconsistent usage of plurals, to having to
use a separate method to "create the formatter" first.
B<PHP>
PHP decided to invent its own date template format. Its C<date()> function
accepts template string in which you specify single letter conversions like C<Y'
(for 4-digit year),>yC<(2-digit year), and so on. Some of the letters mean the
same like their counterpart in strftime, but some are different (examples:>iC<,
>aC<,>M`, and so on). The use of single letter means it's more concise, but the
format becomes unsuitable if you want to put other stuffs (like some string
view release on metacpan or search on metacpan
lib/Acme/CPANModules/Getopt.pm view on Meta::CPAN
auto_help => 1, # from POD
auto_version => 1, # from POD
},
},
{
module => 'Getopt::Lucid',
features => {
uses_spec => 1,
uses_getopt_long => 0,
auto_help => 0,
auto_version => 0,
lib/Acme/CPANModules/Getopt.pm view on Meta::CPAN
=item L<Getopt::Auto>
Author: L<GLEACH|https://metacpan.org/author/GLEACH>
=item L<Getopt::Lucid>
Author: L<DAGOLDEN|https://metacpan.org/author/DAGOLDEN>
=item L<Getopt::ArgvFile>
lib/Acme/CPANModules/Getopt.pm view on Meta::CPAN
| Getopt::Std::Strict | no | no | no | yes | N/A | N/A |
| Getopt::Declare | yes | yes | no | yes | N/A | N/A |
| Getopt::Euclid | yes | yes | no | yes | N/A | N/A |
| Docopt | yes | yes | no | yes | N/A | N/A |
| Getopt::Auto | yes | yes | no | yes | N/A | N/A |
| Getopt::Lucid | no | no | no | yes | N/A | N/A |
| Getopt::ArgvFile | yes | yes | yes | yes | yes | N/A |
| App::Options | yes | yes | no | yes | yes | N/A |
| MooseX::Getopt | yes | yes | yes *9) | yes | no *10) | N/A |
| MooX::Options | yes | no | yes *9) | yes | yes | N/A |
| Getopt::Attribute | yes | yes | yes | yes | N/A | N/A |
view release on metacpan or search on metacpan
lib/Acme/CPANModules/GetoptModules.pm view on Meta::CPAN
auto_help => 1, # from POD
auto_version => 1, # from POD
},
},
{
module => 'Getopt::Lucid',
features => {
uses_spec => 1,
uses_getopt_long => 0,
auto_help => 0,
auto_version => 0,
lib/Acme/CPANModules/GetoptModules.pm view on Meta::CPAN
=item * L<Docopt>
=item * L<Getopt::Auto>
=item * L<Getopt::Lucid>
=item * L<Getopt::ArgvFile>
=item * L<App::Options>
lib/Acme/CPANModules/GetoptModules.pm view on Meta::CPAN
| Getopt::Std::Strict | no | no | no | yes | N/A | N/A |
| Getopt::Declare | yes | yes | no | yes | N/A | N/A |
| Getopt::Euclid | yes | yes | no | yes | N/A | N/A |
| Docopt | yes | yes | no | yes | N/A | N/A |
| Getopt::Auto | yes | yes | no | yes | N/A | N/A |
| Getopt::Lucid | no | no | no | yes | N/A | N/A |
| Getopt::ArgvFile | yes | yes | yes | yes | yes | N/A |
| App::Options | yes | yes | no | yes | yes | N/A |
| MooseX::Getopt | yes | yes | yes *9) | yes | no *10) | N/A |
| MooX::Options | yes | no | yes *11) | yes | yes | N/A |
| Getopt::Attribute | yes | yes | yes | yes | N/A | N/A |
view release on metacpan or search on metacpan
lib/Acme/CPANModules_ScenarioR/HTMLTable.pm view on Meta::CPAN
## no critic
package Acme::CPANModules_ScenarioR::HTMLTable;
our $VERSION = 0.002; # VERSION
our $results = do{my$var=[[200,"OK",[{_name=>"participant=Text::Table::Manifold",_succinct_name=>"TT:M",errors=>4.9e-05,participant=>"Text::Table::Manifold",pct_faster_vs_slowest=>0,pct_slower_vs_fastest=>6.36903376018626,rate=>15.8,samples=>21,time=...
1;
# ABSTRACT: List of modules that generate HTML tables
=head1 DESCRIPTION
view release on metacpan or search on metacpan
lib/Acme/CPANModules/HashUtilities.pm view on Meta::CPAN
%hash = (a=>1, b=>1);
%reverse = reverse %hash; # => sometimes (1=>"b"), sometimes (1=>"a")
<pm:Hash::MoreUtil>'s `safe_reverse` allows you to specify a coderef that can
decide whether to ignore overwriting, croak, or whatever else.
## Slicing (creating subset)
<pm:Hash::MoreUtils>'s `slice_*` functions.
lib/Acme/CPANModules/HashUtilities.pm view on Meta::CPAN
%hash = (a=>1, b=>1);
%reverse = reverse %hash; # => sometimes (1=>"b"), sometimes (1=>"a")
L<Hash::MoreUtil>'s C<safe_reverse> allows you to specify a coderef that can
decide whether to ignore overwriting, croak, or whatever else.
=head2 Slicing (creating subset)
L<Hash::MoreUtils>'s C<slice_*> functions.
view release on metacpan or search on metacpan
lib/Acme/CPANModules/Import/CPANRatings/User/davidgaramond.pm view on Meta::CPAN
our $AUTHORITY = 'cpan:PERLANCAR'; # AUTHORITY
our $DATE = '2023-10-29'; # DATE
our $DIST = 'Acme-CPANModules-Import-CPANRatings-User-davidgaramond'; # DIST
our $VERSION = '0.002'; # VERSION
our $LIST = {description=>"This list is generated by scraping CPANRatings (cpanratings.perl.org) user page.",entries=>[{description=>"\nOk, it's not 2004 anymore, I suggest we retire or start to deprecate this module? This module now requires Perl 5....
1;
# ABSTRACT: List of modules mentioned by CPANRatings user davidgaramond
__END__
lib/Acme/CPANModules/Import/CPANRatings/User/davidgaramond.pm view on Meta::CPAN
Author: L<JTBRAUN|https://metacpan.org/author/JTBRAUN>
Responding to previous comment from MB: "Have you the time to do this Damian?" The answer is yes, in the form of Regexp::Grammars, which Damian said himself is the successor of Parse::RecDescent.
<br><br>To give credit to this module, PRD is very featureful and easy to use, it's very convenient to generate parsers, and the docs is quite complete. The only problem with it is, as many have pointed out, speed.
<br><br>It is I<seriously> slow, with parser generation can take up to half a second on my laptop with a moderate grammar (200-400 lines) and parsing can take seconds even minutes for a moderately long string. It is orders of magnitude slower than ot...
<br><br>For alternatives, try Regexp::Grammars. (Or Parse::Yapp or Parse::EYapp, as other reviewers have written.)
Rating: 6/10
view release on metacpan or search on metacpan
lib/Acme/CPANModules_ScenarioR/OrderedHash.pm view on Meta::CPAN
## no critic
package Acme::CPANModules_ScenarioR::OrderedHash;
our $VERSION = 0.004; # VERSION
our $results = do{my$var=[[200,"OK",[{_name=>"participant=Tie::StoredOrderHash",_succinct_name=>"T:S",errors=>1.4e-06,participant=>"Tie::StoredOrderHash",pct_faster_vs_slowest=>0,pct_slower_vs_fastest=>5.16666666666667,rate=>539,samples=>22,time=>1.8...
1;
# ABSTRACT: List of modules that provide ordered hash data type
=head1 DESCRIPTION
view release on metacpan or search on metacpan
lib/Acme/CPANModules_ScenarioR/TextTable.pm view on Meta::CPAN
## no critic
package Acme::CPANModules_ScenarioR::TextTable;
our $VERSION = 0.016; # VERSION
our $results = do{my$var=[[200,"OK",[{_name=>"participant=Text::UnicodeBox::Table",_succinct_name=>"Text::UnicodeBox::Table",errors=>0.0024,participant=>"Text::UnicodeBox::Table",pct_faster_vs_slowest=>0,pct_slower_vs_fastest=>365.666666666667,rate=>...
1;
# ABSTRACT: List of modules that generate text tables
=head1 DESCRIPTION
view release on metacpan or search on metacpan
lib/Acme/CPANModules_ScenarioR/UUID.pm view on Meta::CPAN
## no critic
package Acme::CPANModules_ScenarioR::UUID;
our $VERSION = 0.011; # VERSION
our $results = [[200,"OK",[{_name=>"participant=UUID::Random::Secure::generate",_succinct_name=>"URS:g",errors=>0.0013,participant=>"UUID::Random::Secure::generate",pct_faster_vs_slowest=>0,pct_slower_vs_fastest=>36.5,rate=>30,samples=>22,time=>30},{...
1;
# ABSTRACT: List of modules that can generate immutable universally unique identifier (UUIDs)
=head1 DESCRIPTION
view release on metacpan or search on metacpan
lib/Acme/CPANModules/VersionNumber/Perl.pm view on Meta::CPAN
each. For example, 1.2.3 becomes 1.002003. 1.20.3 becomes 1.020003. This can
give some surprise which has bitten Perl programmers, novice and expert alike.
In fact, it is the major gotcha when dealing with version numbers in Perl. For
example '0.02' (a decimal form) numifies to 0.02, but 'v0.02' (a dotted decimal
form) numifies to 0.002. Hence, v0.02 is less than 0.02 or even 0.01 when
compared using version->parse(). Another gotcha is when a module author decides
to go from 0.02 to 0.2.1 or 0.02.1. 0.02 (a decimal form) numifies to 0.02 while
0.2.1 or 0.02.1 (dotted decimal) numifies to 0.002001. Hence, going from 0.02 to
0.02.1 will actually *decrease* your version number. I recommend using x.yyy if
you use decimal form, i.e. start from 0.001 and not 0.01. It will support you
going smoothly to dotted decimal if you decide to do it one day.
The numification is also problematic when a number part is > 999, e.g. 1.2.1234.
This breaks version comparison when comparison is done with version->parse().
Aside from the abovementioned two styles, there is another: CPAN
lib/Acme/CPANModules/VersionNumber/Perl.pm view on Meta::CPAN
each. For example, 1.2.3 becomes 1.002003. 1.20.3 becomes 1.020003. This can
give some surprise which has bitten Perl programmers, novice and expert alike.
In fact, it is the major gotcha when dealing with version numbers in Perl. For
example '0.02' (a decimal form) numifies to 0.02, but 'v0.02' (a dotted decimal
form) numifies to 0.002. Hence, v0.02 is less than 0.02 or even 0.01 when
compared using version->parse(). Another gotcha is when a module author decides
to go from 0.02 to 0.2.1 or 0.02.1. 0.02 (a decimal form) numifies to 0.02 while
0.2.1 or 0.02.1 (dotted decimal) numifies to 0.002001. Hence, going from 0.02 to
0.02.1 will actually I<decrease> your version number. I recommend using x.yyy if
you use decimal form, i.e. start from 0.001 and not 0.01. It will support you
going smoothly to dotted decimal if you decide to do it one day.
The numification is also problematic when a number part is > 999, e.g. 1.2.1234.
This breaks version comparison when comparison is done with version->parse().
Aside from the abovementioned two styles, there is another: CPAN
view release on metacpan or search on metacpan
lib/Acme/CPANModules.pm view on Meta::CPAN
A related website/online service for "CPAN modules" is coming (when I eventually
get to it :-), or perhaps when I get some help).
=head1 CREATING AN ACME::CPANMODULES MODULE
The first step is to decide on the name of your module. It must be under the
C<Acme::CPANModules::> namespace. For example, if you create a list of your
favorite modules, you can use C<Acme::CPANModules::YOURCPANID::Favorite>. Or if
you are creating a list of modules that predict the future, you can choose
C<Acme::CPANModules::PredictingTheFuture>. See recommendations for module name
in L</module name> under L</RECOMMENDATIONS>.
view release on metacpan or search on metacpan
devdata/https_mojolicious.io_blog_2017_12_03_day-3-using-named-routes view on Meta::CPAN
The following arguments build the url by name and placeholder value(s).
The return is actually a <a href="http://mojolicious.org/perldoc/Mojo/URL">Mojo::URL</a> so if you need to add other things like query parameters, that can be done afterwards.</p>
<h2>Changing the Routes</h2>
<p>Everything was fine until one day Santa decided that he wanted show off some of the year's new toys too.
The problem was that he hadn't planned his urls for that.
He could just keep all the existing ones and add a special cased <code>/toys</code> route, but it would look silly that way.
What he really needed to do was move all of the staff pages to keep the urls consistent.</p>
<pre><code>use Mojolicious::Lite;
view release on metacpan or search on metacpan
devdata/https_mojolicious.io_blog_2018_12_01_welcome-mojoconf-recap_ view on Meta::CPAN
<section id="section-2">
<h2>Sidetrip to Western Norway</h2>
<p>On a personal note, I especially enjoyed this trip because I was able to take a few extra days to visit the West of Norway, home to the iconic fjords.
I visited Bergen and several of its Perlers before taking a fjord tour by boat and train.
It would have been the perfect trip if my bag hadn't decided that it wanted to stay an extra few days in Iceland where I'd had a delayed stop-over.</p>
<p>Still I had an amazing times and saw once in a lifetime sights!
Thanks to Christopher and Jonis and all the people whoe were my companions for the trip!</p>
<h2>Nordic Perl Workshop and MojoConf</h2>
view release on metacpan or search on metacpan
lib/Acme/CPANModules/Import/PERLANCAR/GetoptModules.pm view on Meta::CPAN
{ module => "Getopt::Compact" },
{ module => "Docopt" },
{ module => "Getopt::Euclid" },
{ module => "Opt::Imistic" },
{ module => "overload" },
{ module => "Getopt::Lucid" },
{ module => "Getopt::Std::Strict" },
{ module => "Getopt::Declare" },
{ module => "Getopt::Long::More" },
{ module => "Getopt::Simple" },
{ module => "Getopt::Tiny" },
lib/Acme/CPANModules/Import/PERLANCAR/GetoptModules.pm view on Meta::CPAN
=item * L<Opt::Imistic>
=item * L<overload>
=item * L<Getopt::Lucid>
=item * L<Getopt::Std::Strict>
=item * L<Getopt::Declare>
view release on metacpan or search on metacpan
devdata/http_advent.perldancer.org_2018_15 view on Meta::CPAN
<div id="content">
<div class="pod-document"><h1><a name="dancer2__plugin__paginator___born_again"></a>Dancer2::Plugin::Paginator - Born Again</h1>
<h2><a name="history"></a>HISTORY</h2>
<p>I would call it re-birth. It all started during end of July 2017, I was going through the documentation of <a href="https://metacpan.org/pod/distribution/Dancer2/lib/Dancer2/Plugins.pod">Dancer2::Plugins</a> and stumbled upon <a href="https://meta...
<h2><a name="rebirth"></a>REBIRTH</h2>
<p>Following the <a href="http://neilb.org/2014/01/31/adoption-request.html">advise</a> from Neil Bowers, I contacted the author <b>Blabos de Blebe</b> by email, if he was happy for me take it forward. He not only encouraged me but also gave me permi...
<h2><a name="challenge"></a>CHALLENGE</h2>
view release on metacpan or search on metacpan
Acme-Can't-0.01/README view on Meta::CPAN
A README file is required for CPAN modules since CPAN extracts the
README file from a module distribution so that people browsing the
archive can use it get an idea of the modules uses. It is usually a
good idea to provide version information here so that people can
decide whether fixes for the module are worth downloading.
INSTALLATION
To install this module type the following:
view release on metacpan or search on metacpan
that should be provided before the module is installed.
A README file is required for CPAN modules since CPAN extracts the README
file from a module distribution so that people browsing the archive
can use it to get an idea of the module's uses. It is usually a good idea
to provide version information here so that people can decide whether
fixes for the module are worth downloading.
INSTALLATION
view release on metacpan or search on metacpan
lib/Acme/Cat/Schroedinger.pm view on Meta::CPAN
When you create the cat, it has the following properties:
=head3 temperament = cooperative
Allowed: C<cooperative|perverse|random>. Determines whether the cat always behaves the way you ask it to, never behaves the way you ask it to, or decides how to behave only when you ask it.
=head1 BUGS
If you're clever, you can work out that the object in question is a cat, and furthermore you might be able to work out its temperament, mutability, etc.
view release on metacpan or search on metacpan
inc/Module/Install.pm view on Meta::CPAN
use strict 'vars';
use vars qw{$VERSION $MAIN};
BEGIN {
# All Module::Install core packages now require synchronised versions.
# This will be used to ensure we don't accidentally load old or
# different versions of modules.
# This is not enforced yet, but will be some time in the next few
# releases once we can make sure it won't clash with custom
# Module::Install extensions.
$VERSION = '0.91';
view release on metacpan or search on metacpan
examples/japh.chef view on Meta::CPAN
44 potatoes
114 onions
101 g flour
107 kg salt
99 bottles of beer
97 cups acid
72 l oil
32 pins
8 l urine
108 pines
101 laptops
examples/japh.chef view on Meta::CPAN
74 creeps
Method.
Put potatoes into the mixing bowl. Put onions into the mixing bowl. Put
flour into the mixing bowl. Put salt into the mixing bowl. Put bottles
of beer into the mixing bowl. Put acid into the mixing bowl. Put oil into
the mixing bowl. Put pins into the mixing bowl. Put pines into the
mixing bowl. Put onions into the mixing bowl. Put laptops into the mixing
bowl. Put mouses into the mixing bowl. Put keyboards into the mixing
bowl. Put idiots into the mixing bowl. Put flour into the mixing bowl.
Put hackers into the mixing bowl. Put voodoo puppets into the mixing
view release on metacpan or search on metacpan
=head1 SYNOPSIS
package Jugarum;
use Acme::Class::Std;
package main;
my $obj = Jugarum->new; # Can't accidentally be serialised.
=head1 DESCRIPTION
Class::Std's inside out objects are wonderful, but all the common
serialisation packages assume that because they can see inside them, they
view release on metacpan or search on metacpan
inc/Module/Install.pm view on Meta::CPAN
use File::Path ();
use vars qw{$VERSION $MAIN};
BEGIN {
# All Module::Install core packages now require synchronised versions.
# This will be used to ensure we don't accidentally load old or
# different versions of modules.
# This is not enforced yet, but will be some time in the next few
# releases once we can make sure it won't clash with custom
# Module::Install extensions.
$VERSION = '1.06';
view release on metacpan or search on metacpan
inc/Module/Install.pm view on Meta::CPAN
use strict 'vars';
use vars qw{$VERSION};
BEGIN {
# All Module::Install core packages now require synchronised versions.
# This will be used to ensure we don't accidentally load old or
# different versions of modules.
# This is not enforced yet, but will be some time in the next few
# releases once we can make sure it won't clash with custom
# Module::Install extensions.
$VERSION = '0.67';
view release on metacpan or search on metacpan
lib/Acme/ConspiracyTheory/Random.pm view on Meta::CPAN
my $redstring = shift // {};
my $chemicals = _RANDOM_(
'oestrogen',
'testosterone',
'acid',
'birth-control',
'fertilizer',
'Diet Coke',
'heavy hydrogen',
'5G',
lib/Acme/ConspiracyTheory/Random.pm view on Meta::CPAN
"Isn't it obvious?",
"Wake up, sheeple!",
"It's obvious if you connect the dots.",
"They leave clues to mock us.",
"It's not funny!",
"There are too many coincidences to ignore.",
"You'd have to be blind not to see it!",
"It's so obvious!",
);
_MERGE_( $redstring, clone => $x );
lib/Acme/ConspiracyTheory/Random.pm view on Meta::CPAN
},
sub {
shady_group( $redstring );
$redstring->{antagonist} //= $redstring->{shady_group};
$redstring->{topic} = { name => 'avalanches', plural => 1 };
$redstring->{antagonist}{name} . " was responsible for the Dyatlov Pass incident";
},
sub {
$redstring->{topic} = { name => 'Jeffrey Epstein', plural => 0 };
"Epstein didn't kill himself";
},
lib/Acme/ConspiracyTheory/Random.pm view on Meta::CPAN
my $subst = _RANDOM_(
'TikTok',
'Twitter',
'the world wars',
'intergalactic warfare',
'the white genocide',
'colonization',
'robot wars',
);
"the crusades never stopped, they were just replaced with $subst";
},
lib/Acme/ConspiracyTheory/Random.pm view on Meta::CPAN
my $solution = _UCFIRST_ _RANDOM_(
"They paid $group to kill him.",
"$group helped cover up the truth.",
"$group threatened to kill him to keep him quiet.",
"He was a member of $group so they knew he would keep quiet.",
"$group arranged a convenient \"accident\".",
);
my $destruction = _RANDOM_(
"all of modern physics",
'our understanding of the universe',
lib/Acme/ConspiracyTheory/Random.pm view on Meta::CPAN
my $solution = _UCFIRST_ _RANDOM_(
"They paid $group to kill him.",
"$group helped cover up the truth.",
"$group threatened to kill him to keep him quiet.",
"He was a member of $group so they knew he would keep quiet.",
"$group arranged a convenient \"accident\".",
);
my $destruction = _RANDOM_(
"the 'theory' of evolution",
'modern medicine',
lib/Acme/ConspiracyTheory/Random.pm view on Meta::CPAN
my $silence = _RANDOM_(
"$pronoun will probably have to be eliminated",
"$pronoun is going to be killed if $pronoun isn't dead already",
"$pronoun is being paid to stay quiet",
"$pronoun will meet a convenient \"accident\"",
sub {
my $clone = clone( $redstring );
"$pronoun has been replaced by $clone";
},
sub {
view release on metacpan or search on metacpan
inc/Module/Install.pm view on Meta::CPAN
use strict 'vars';
use vars qw{$VERSION $MAIN};
BEGIN {
# All Module::Install core packages now require synchronised versions.
# This will be used to ensure we don't accidentally load old or
# different versions of modules.
# This is not enforced yet, but will be some time in the next few
# releases once we can make sure it won't clash with custom
# Module::Install extensions.
$VERSION = '0.91';
view release on metacpan or search on metacpan
lib/Acme/CreatingCPANModules.pm view on Meta::CPAN
[slide] Here's a Changes file.
Note that the order of the changes is chronologically inversed. Why?
Because the purporse of a changes file is (among others) to let the
user know what you changed from the last version, so that he can
decide if he wants to install your module.
Hence, and since browsers and editors usually open files in their
beginning, it's only reasonable that you put the most recent changes
on the top of the file.