view release on metacpan or search on metacpan
lib/POE/Component/Server/IRC.pm view on Meta::CPAN
my $count = @$args;
# - parv[0] = nickname
# - parv[1] = TS
# - parv[2] = [-][raw]
# - parv[3] = required user mode(s) to see the tag
# - parv[4] = tag line
SWITCH: {
if (!$self->_state_sid_serv($prefix) && $prefix ne $sid) {
last SWITCH;
view release on metacpan or search on metacpan
footer = | close FH;
footer = |}
[DynamicPrereqs]
-condition = prompt_default_no('Do you want encryption ( requires Mcrypt )')
-body = requires( 'Mcrypt' => '2.5.7.0' );
[Prereqs / TestRequires]
Test::More = 0.47
[Prereqs]
view release on metacpan or search on metacpan
[@BINGOS]
[DynamicPrereqs]
-condition = prompt_default_no('Do you want to install optional module File::LibMagic')
-body = requires('File::LibMagic','1.15')
[Prereqs / ConfigureRequires]
ExtUtils::MakeMaker = 0
[Prereqs / BuildRequires]
view release on metacpan or search on metacpan
[@BINGOS]
[DynamicPrereqs]
-condition = is_os('MSWin32')
-body = requires( 'POE::Wheel::Run::Win32' => 0.10 );
-body = requires( 'Win32API::File' => 0 );
[Prereqs / TestRequires]
Test::Harness = 3.14
Test::More = 0.47
view release on metacpan or search on metacpan
[Git::Commit]
[Git::Tag]
[Git::Push]
[Prereqs / ConfigureRequires]
-phase = configure
-type = requires
Devel::CheckLib = 0
view release on metacpan or search on metacpan
[Git::Tag]
[Git::Push]
[Prereqs / ConfigureRequires]
-phase = configure
-type = requires
Devel::CheckLib = 0
[Prereqs / TestRecommends]
-phase = test
-type = recommends
Signal::Mask = 0
view release on metacpan or search on metacpan
Makefile.PL view on Meta::CPAN
But, it's more interesting than that. You can load it with C<require>
and call C<arguments> to get the data structure it passes to
C<WriteMakefile>:
my $package = require '/path/to/Makefile.PL';
my $arguments = $package->arguments;
Note that C<require>-ing a file makes an entry in C<%INC> for exactly
that name. If you try to C<require> another file with the same name,
even from a different path, C<require> thinks it has already loaded
view release on metacpan or search on metacpan
Makefile.PL view on Meta::CPAN
But, it's more interesting than that. You can load it with C<require>
and call C<arguments> to get the data structure it passes to
C<WriteMakefile>:
my $package = require '/path/to/Makefile.PL';
my $arguments = $package->arguments;
Note that C<require>-ing a file makes an entry in C<%INC> for exactly
that name. If you try to C<require> another file with the same name,
even from a different path, C<require> thinks it has already loaded
view release on metacpan or search on metacpan
[Prereqs / TestRequires]
Test::More = 0.96
[DynamicPrereqs]
-body = requires('File::Spec', is_os('MSWin32') ? '3.2701' : '0.84');
-body = requires('IO::String') if $] < '5.008000';
[Git::GatherDir]
exclude_filename = README.pod
[MetaYAML]
[MetaJSON]
view release on metacpan or search on metacpan
Test::MinimumVersion.max_target_perl = 5.008001
; authordep ExtUtils::HasCompiler = 0.014
[DynamicPrereqs]
:version = 0.029
-body = requires('Package::Stash::XS', '0.26') if !want_pp() and can_xs();
; authordep Dist::Zilla::Plugin::SurgicalPodWeaver
[Prereqs / TestRequires]
Test::More = 0.88
view release on metacpan or search on metacpan
[RemovePrereqs::Provided / @Author::KENTNL/RemovePrereqs::Provided]
[Prereqs / @Author::KENTNL/::Role::BundleDeps]
; twitter_extra_hash_tags =
-phase = develop
-relationship = requires
Dist::Zilla::Plugin::Author::KENTNL::RecommendFixes = 0.004002
Dist::Zilla::Plugin::Author::KENTNL::TravisCI = 0.001002
Dist::Zilla::Plugin::Authority = 1.006
Dist::Zilla::Plugin::AutoPrereqs = 0
Dist::Zilla::Plugin::BumpVersionAfterRelease = 0
view release on metacpan or search on metacpan
lib/Panda/Install/Payload.pm view on Meta::CPAN
my $module = shift;
my $info = $module_info{$module};
unless ($info) {
my $file = module_info_file($module) or return undef;
return undef unless -f $file;
$info = require $file or return undef;
$module_info{$module} = $info;
}
return $info;
}
view release on metacpan or search on metacpan
; version_rel_hour = 1
; version_rel_time_zone = Pacific/Auckland
; twitter_extra_hash_tags =
; auto_prereqs_skip = File::Find
-phase = develop
-relationship = requires
Dist::Zilla::Plugin::Author::KENTNL::RecommendFixes = 0.004002
Dist::Zilla::Plugin::Author::KENTNL::TravisCI = 0.001002
Dist::Zilla::Plugin::Authority = 1.006
Dist::Zilla::Plugin::AutoPrereqs = 0
Dist::Zilla::Plugin::BumpVersionAfterRelease = 0
view release on metacpan or search on metacpan
; version_rel_hour = 4
; version_rel_time_zone = Pacific/Auckland
; twitter_extra_hash_tags =
; auto_prereqs_skip = File::Find
-phase = develop
-relationship = requires
Dist::Zilla::Plugin::Author::KENTNL::RecommendFixes = 0.004002
Dist::Zilla::Plugin::Author::KENTNL::TravisCI = 0.001002
Dist::Zilla::Plugin::Authority = 1.006
Dist::Zilla::Plugin::AutoPrereqs = 0
Dist::Zilla::Plugin::BumpVersionAfterRelease = 0
view release on metacpan or search on metacpan
[RemovePrereqs::Provided / @Author::KENTNL/RemovePrereqs::Provided]
[Prereqs / @Author::KENTNL/::Role::BundleDeps]
-phase = develop
-relationship = requires
Dist::Zilla::Plugin::Author::KENTNL::RecommendFixes = 0.004002
Dist::Zilla::Plugin::Author::KENTNL::TravisCI = 0.001002
Dist::Zilla::Plugin::Authority = 1.006
Dist::Zilla::Plugin::AutoPrereqs = 0
Dist::Zilla::Plugin::BumpVersionAfterRelease = 0
view release on metacpan or search on metacpan
Makefile.PL view on Meta::CPAN
But, it's more interesting than that. You can load it with C<require>
and call C<arguments> to get the data structure it passes to
C<WriteMakefile>:
my $package = require '/path/to/Makefile.PL';
my $arguments = $package->arguments;
Note that C<require>-ing a file makes an entry in C<%INC> for exactly
that name. If you try to C<require> another file with the same name,
even from a different path, C<require> thinks it has already loaded
view release on metacpan or search on metacpan
t/CodeLayout/ProhibitLongLines/gitattributes.t view on Meta::CPAN
skip "could not initialise git repo" unless $dir;
$dir
}
sub test_ignore_attribute () {
my $dir = require_git();
my $policy = Perl::Critic::Policy::CodeLayout::ProhibitLongLines->new;
my $path = write_perl_file($dir, "ignore.t", "$Long_line\n");
my @v = violations_for_file($policy, $path);
is scalar @v, 0, "no violations when attribute is ignore";
}
sub test_numeric_attribute () {
my $dir = require_git();
my $policy = Perl::Critic::Policy::CodeLayout::ProhibitLongLines->new;
# 81-char line is fine under limit of 200
my $path = write_perl_file($dir, "wide.t", "$Long_line\n");
t/CodeLayout/ProhibitLongLines/gitattributes.t view on Meta::CPAN
@v = violations_for_file($policy, $path);
is scalar @v, 1, "201-char line exceeds 200-char override";
}
sub test_unspecified_attribute () {
my $dir = require_git();
my $policy = Perl::Critic::Policy::CodeLayout::ProhibitLongLines->new;
# normal.t has no gitattributes entry, so default 80 applies
my $path = write_perl_file($dir, "normal.t", "$Long_line\n");
t/CodeLayout/ProhibitLongLines/gitattributes.t view on Meta::CPAN
my @v = $policy->violates($doc, $doc);
is scalar @v, 1, "string input (no filename) uses default limit";
}
sub test_feature_disabled () {
my $dir = require_git();
my $policy = Perl::Critic::Policy::CodeLayout::ProhibitLongLines->new;
$policy->{_gitattributes_line_length} = "";
# ignore.t would be ignored if the feature were active
t/CodeLayout/ProhibitLongLines/gitattributes.t view on Meta::CPAN
my @v = violations_for_file($policy, $path);
is scalar @v, 1, "violations reported when feature is disabled";
}
sub test_get_gitattr_line_length () {
my $dir = require_git();
my $policy = Perl::Critic::Policy::CodeLayout::ProhibitLongLines->new;
# Need actual files for git check-attr
write_perl_file($dir, "ignore.t", "1;\n");
view release on metacpan or search on metacpan
[RecommendedPrereqs]
[AutoPrereqs]
[Prereqs / BuildRequires ]
-phase = build
-relationship = requires
ExtUtils::MakeMaker = 7.22
Module::Metadata = 1.000015
[Prereqs / DevelopRequires ]
-phase = develop
-relationship = requires
ExtUtils::Manifest = 1.68
Test::CPAN::Changes = 0
Test::Vars = 0.015
; [EnsurePrereqsInstalled]
; :version = 0.003
; type = requires
; type = recommends
[SecurityPolicy]
-policy = Individual
-policy_version = 0.10
view release on metacpan or search on metacpan
Makefile.PL view on Meta::CPAN
But, it's more interesting than that. You can load it with C<require>
and call C<arguments> to get the data structure it passes to
C<WriteMakefile>:
my $package = require '/path/to/Makefile.PL';
my $arguments = $package->arguments;
Note that C<require>-ing a file makes an entry in C<%INC> for exactly
that name. If you try to C<require> another file with the same name,
even from a different path, C<require> thinks it has already loaded
view release on metacpan or search on metacpan
examples/tutorial_gen/tut.pl view on Meta::CPAN
$conf_fp = "$path/conf.pl";
}
say ~$path if $dg;
# todo_ require problem
#my $conf_raw = require $conf_fp || die "Conf file '$conf_fp' not loaded;";
#my %conf = hash( $conf_raw );
my %conf = {
index => [
view release on metacpan or search on metacpan
Makefile.PL view on Meta::CPAN
But, it's more interesting than that. You can load it with C<require>
and call C<arguments> to get the data structure it passes to
C<WriteMakefile>:
my $package = require '/path/to/Makefile.PL';
my $arguments = $package->arguments;
Note that C<require>-ing a file makes an entry in C<%INC> for exactly
that name. If you try to C<require> another file with the same name,
even from a different path, C<require> thinks it has already loaded
view release on metacpan or search on metacpan
Makefile.PL view on Meta::CPAN
But, this F<Makefile.PL> is more interesting than that. You can load
it with C<require> and call C<arguments> to get the data structure it
passes to C<WriteMakefile>:
my $package = require '/path/to/Makefile.PL';
my $arguments = $package->arguments;
Note that C<require>-ing a file makes an entry in C<%INC> for exactly
that name. If you try to C<require> another file with the same name,
even from a different path, C<require> thinks it has already loaded
view release on metacpan or search on metacpan
[Prereqs / TestRequires]
[EnsurePrereqsInstalled]
:version = 0.003
type = requires
type = recommends
[GitHub::Meta]
repo = git://github.com/robrwo/PerlX-Let.git
view release on metacpan or search on metacpan
lib/Perlbal/Manual/HighPriority.pod view on Meta::CPAN
Perlbal can use cookies to determine if a request should go to the high priority queue (configurable).
The parameters to configure this are C<high_priority_cookie> and C<high_priority_cookie_contents>; the first defines the name of the field to check for on the cookie and the second one defines the content in that field that will trigger the request g...
SET myservice.high_priority_cookie = name_of_the_field
SET myservice.high_priority_cookie_contents = required_content_on_that_field
Here's a clearer example:
SET myservice.high_priority_cookie = highpriority
SET myservice.high_priority_cookie_contents = yes
view release on metacpan or search on metacpan
lib/Perlito5/JavaScript2/CORE.pm view on Meta::CPAN
# sleep()
. <<'EOT'
if (isNode) {
try {
var sleep = require("sleep");
CORE.sleep = function(List__) {
var n = p5num(List__[0]) || 1;
sleep.usleep(n * 1000000); // sleep for n seconds (1 second is 1000000 microseconds)
return n;
}
lib/Perlito5/JavaScript2/CORE.pm view on Meta::CPAN
# crypt()
. <<'EOT'
if (isNode) {
try {
var crypt = require("crypt3");
CORE.crypt = function(List__) {
var text = p5str(List__[0]);
var salt = p5str(List__[1]);
while(salt.length < 2) {
salt += "A";
view release on metacpan or search on metacpan
lib/Pickles/Config.pm view on Meta::CPAN
my $path_to = sub { $self->path_to(@_) };
my $load_file = sub {
my $file = $path_to->( @_ );
delete $INC{$file};
my $subconf = require $file;
# death context should be at the calling config file level
Carp::croak("Could not parse $file: $@") if $@;
Carp::croak("Could not do $file: $!") if ! defined $subconf;
Carp::croak("Could not run $file") if ! $subconf;
lib/Pickles/Config.pm view on Meta::CPAN
}
my $config_pkg = sprintf <<'SANDBOX', $fqname;
package %s;
{
my $conf = require $file or die $!;
$conf;
}
SANDBOX
delete $INC{$file};
my $conf = eval $config_pkg || +{};
view release on metacpan or search on metacpan
use strict;
print "1..3\n";
my $ok = require RPC::PlServer::Comm;
printf("%sok 1\n", ($ok ? "" : "not "));
$ok = require RPC::PlServer;
printf("%sok 2\n", ($ok ? "" : "not "));
$ok = require RPC::PlClient;
printf("%sok 3\n", ($ok ? "" : "not "));
view release on metacpan or search on metacpan
[RecommendedPrereqs]
[AutoPrereqs]
[EnsurePrereqsInstalled]
:version = 0.003
type = requires
type = recommends
[GitHub::Meta]
repo = git://github.com/robrwo/perl-Plack-App-Prerender.git
view release on metacpan or search on metacpan
share/js/jquery.js view on Meta::CPAN
// For CommonJS and CommonJS-like environments where a proper window is present,
// execute the factory and get jQuery
// For environments that do not inherently posses a window with a document
// (such as Node.js), expose a jQuery-making factory as module.exports
// This accentuates the need for the creation of a real window
// e.g. var jQuery = require("jquery")(window);
// See ticket #14549 for more info
module.exports = global.document ?
factory( global, true ) :
function( w ) {
if ( !w.document ) {
view release on metacpan or search on metacpan
lib/Plack/Middleware/Assets/RailsLike.pm view on Meta::CPAN
The Manifest syntax is same as Rails Asset Pipeline, but only support
C<require> command.
> vim ./htdocs/assets/main-page.js
> cat ./htdocs/assets/main-page.js
//= require jquery
//= require myapp
Next, write URLs of manifest file to your html. This middleware supports
versioning. So you can add version string in between its file basename and
suffix.