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
remove = IO::Handle
remove = Module::Load
[EnsurePrereqsInstalled]
:version = 0.003
type = requires
type = recommends
[GitHub::Meta]
repo = git://github.com/bigpresh/Pod-Readme.git
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
lib/Pod/Weaver/PluginBundle/Author/KENTNL.pm view on Meta::CPAN
-~- Inherited from @Author::KENTNL::Collectors -~-
; command[].default = [ required function attr method pfunction pattr pmethod ]
; command[].entry_type[0] = KNOWNCOMMANDNAME
; command[].entry_type[1] = COMMANDNAME = DESCRIPTION
; KNOWNCOMMANDNAME.enums =
; = required ; REQUIRED METHODS
; = function ; FUNCTIONS
; = method ; METHODS
; = attr ; ATTRIBUTES
; = cattr ; ATTRIBUTES / CONSTRUCTOR ARGUMENTS
; = pfuncton ; PRIVATE FUNCTIONS
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
lib/QBit/Validator/Type/hash.pm view on Meta::CPAN
return 0;
}
}
#TODO: implement method _exists
# defined = required
sub fields {
my ($qv, $fields, $template) = @_;
my $parent = $qv->parent // $qv;
view release on metacpan or search on metacpan
lib/Qgoda/Command/Javascript.pm view on Meta::CPAN
are accepted by Duktape!
Qgoda, however, implements a module resolver so that you can use constructs
like:
const _ = require('lodash');
The module is resolved in the same way that NodeJS would resolve it.
See the option I<--global> below for more information.
=head1 OPTIONS
view release on metacpan or search on metacpan
foreach(@files) {
my %test = ( file => $_ );
logger("loading $_... ");
$test{cb} = require $_;
logger("done\n");
push(@buf, \%test);
}
view release on metacpan or search on metacpan
;version_rel_month = 12
;version_rel_day = 25
;version_rel_hour = 13
;version_rel_time_zone = Pacific/Auckland
-phase = develop
-relationship = requires
Dist::Zilla::Plugin::Author::KENTNL::CONTRIBUTING = 0.001003
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
view release on metacpan or search on metacpan
lib/Repo/html/requires_tree_html.template view on Meta::CPAN
var div = d3.select(document.getElementById( 'front_wrapper' )).append("div")
.attr("class", "tree-tooltip")
.style("opacity", 0);
d3.json("@JSON_DATA_FILE@", function(error, requires) {
root = requires;
root.x0 = height / 2;
root.y0 = 0;
function collapse(d) {
if (d.children) {
view release on metacpan or search on metacpan
lib/Require/Util.pm view on Meta::CPAN
if (try_require "Foo::Bar") {
# use Foo::Bar's function
}
my $modname = require_any "Foo::Bar", "Baz/Qux.pm", "Quux";
=head1 DESCRIPTION
B<EXPERIMENTAL.>
lib/Require/Util.pm view on Meta::CPAN
=head2 require_any
Usage:
my $res = require_any $modname1, $modname2, ...;
Example:
my $res = require_any "Foo::Bar", "Baz/Qux.pm";
Require modules listed as arguments, stopping after the first success. If all
modules cannot be loaded, will die. Module name can be specified as C<Foo::Bar>
syntax or as C<Foo/Bar.pm> syntax. Unlike C<require()> which just returns true,
upon success the function will return the module name that gets 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
lib/Rewire/Engine.pm view on Meta::CPAN
# FUNCTIONS
# returns the json-schema-based engine ruleset
fun ruleset() {
state $ruleset = require Rewire::Ruleset;
}
# returns context closure
fun context() {
my $cache = {};
view release on metacpan or search on metacpan
remove = strict
remove = warnings
[EnsurePrereqsInstalled]
:version = 0.003
type = requires
type = recommends
[GitHub::Meta]
repo = git://github.com/robrwo/Robots-Validate.git
view release on metacpan or search on metacpan
vendor/rocksdb/tools/rdb/rdb view on Meta::CPAN
#!/usr/bin/env bash
node -e "RDB = require('./build/Release/rdb').DBWrapper; console.log('Loaded rocksdb in variable RDB'); repl = require('repl').start('> ');"
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
lib/SPVM/Resource/Eigen.native/include/Eigen/src/Core/arch/SYCL/SyclMemoryModel.h view on Meta::CPAN
typename pointerMap_t::iterator retVal;
bool reuse = false;
if (!m_freeList.empty()) {
// try to re-use an existing block
for (auto freeElem : m_freeList) {
if (freeElem->second.m_size >= requiredSize) {
retVal = freeElem;
reuse = true;
// Element is not going to be free anymore
m_freeList.erase(freeElem);
break;
view release on metacpan or search on metacpan
.tmp/libpng/scripts/options.awk view on Meta::CPAN
}
}
} else if (val == "requires" || val == "if" || val == "enables" || val =="sets") {
key = val
} else if (key == "requires") {
requires[opt] = requires[opt] " " val
} else if (key == "if") {
iffs[opt] = iffs[opt] " " val
} else if (key == "enables") {
enabledby[val] = enabledby[val] " " opt
} else if (key == "sets") {
view release on metacpan or search on metacpan
lib/SPVM/Resource/RE2.native/src/.github/workflows/pr.yml view on Meta::CPAN
steps:
- uses: actions/checkout@v3
- uses: actions/github-script@v6
with:
script: |
const fs = require('fs');
console.log(await github.rest.issues.createComment({
owner: context.repo.owner,
repo: context.repo.repo,
issue_number: context.issue.number,
body: fs.readFileSync('CONTRIBUTING.md', { encoding: 'utf8', }),
view release on metacpan or search on metacpan
lib/SPVM/Builder/src/spvm_op.c view on Meta::CPAN
}
}
args_length++;
}
method->args_length = args_length;
method->required_args_length = required_args_length;
}
// Variable declarations of arguments
SPVM_OP* op_arg = op_args->first;
while ((op_arg = SPVM_OP_sibling(compiler, op_arg))) {
view release on metacpan or search on metacpan
lib/SQL/Admin/Driver/DB2/Parser.pm view on Meta::CPAN
use SQL::Admin::Utils qw( refhash refarray );
######################################################################
my $grammar = require SQL::Admin::Driver::DB2::Grammar;
my $cached;
######################################################################
######################################################################
sub new { # ;
view release on metacpan or search on metacpan
t/900_regtest.t view on Meta::CPAN
if ( $@ ) {
diag "$api not installed";
skip "$api not installed, skipping tests", $tests = 1;
}
-d "t" && chdir "t";
$tests = require "./900_regtest.pl";
}
done_testing($tests);
view release on metacpan or search on metacpan
t/eval_barrier.t view on Meta::CPAN
push @events, ["b0"];
@value = sub {
push @events, ["c0"];
$cont = current_escape_function;
push @events, ["c1"];
@value = require("t/eval_barrier_req.pl");
push @events, ["c3", [@value]];
("c4a", "c4b");
}->();
push @events, ["b1", [@value]];
("b2a", "b2b");
view release on metacpan or search on metacpan
;version_rel_month = 8
;version_rel_day = 26
;version_rel_hour = 00
;version_rel_time_zone = Pacific/Auckland
-phase = develop
-relationship = requires
Dist::Zilla::Plugin::Author::KENTNL::CONTRIBUTING = 0.001003
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
view release on metacpan or search on metacpan
t/Firefox-Profile.t view on Meta::CPAN
# This extension rewrites any page url to a single <h1>. The
# following javascript is in redisplay.xpi's
# resources/gempesaw/lib/main.js:
# var pageMod = require("sdk/page-mod");
# pageMod.PageMod({
# include: "*",
# contentScript: 'document.body.innerHTML = ' +
# ' "<h1>Page matches ruleset</h1>";'
# });
view release on metacpan or search on metacpan
remove = warnings
remove = utf8
[EnsurePrereqsInstalled]
:version = 0.003
type = requires
type = recommends
[GitHub::Meta]
repo = git@github.com:robrwo/SemanticWeb-Schema.git
view release on metacpan or search on metacpan
; version_rel_day = 24
; version_rel_hour = 16
; version_rel_time_zone = Pacific/Auckland
; auto_prereqs_skip = File::Find
-phase = develop
-relationship = requires
Dist::Zilla::Plugin::Author::KENTNL::CONTRIBUTING = 0.001003
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
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.62
[EnsurePrereqsInstalled]
:version = 0.003
type = requires
type = recommends
[GitHub::Meta]
repo = git://github.com/robrwo/Set-Light.git