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 all matches for this distribution
view release on metacpan or search on metacpan
RungeKutta.pm view on Meta::CPAN
In the C<lua/> subdirectory of the install directory there is
I<RungeKutta.lua>, which is an exact translation of this Perl code into Lua.
The function names and arguments are unchanged.
Brief Synopsis:
local RK = require 'RungeKutta'
function dydt(t, y) -- the derivative function
-- y is the table of the values, dydt the table of the derivatives
local dydt = {}; ... ; return dydt
end
y = initial_y(); t=0; dt=0.4; -- the initial conditions
view all matches for this distribution
view release on metacpan or search on metacpan
Ryu_Library/ryu/d2fixed.c view on Meta::CPAN
if (lastDigit != 5) {
roundUp = lastDigit > 5;
} else {
// Is m * 10^(additionalDigits + 1) / 2^(-e2) integer?
const int32_t requiredTwos = -e2 - (int32_t) precision - 1;
const bool trailingZeros = requiredTwos <= 0
|| (requiredTwos < 60 && multipleOfPowerOf2(m2, (uint32_t) requiredTwos));
roundUp = trailingZeros ? 2 : 1;
#ifdef RYU_DEBUG
printf("requiredTwos=%d\n", requiredTwos);
printf("trailingZeros=%s\n", trailingZeros ? "true" : "false");
Ryu_Library/ryu/d2fixed.c view on Meta::CPAN
} else {
// Is m * 2^e2 * 10^(precision + 1 - exp) integer?
// precision was already increased by 1, so we don't need to write + 1 here.
const int32_t rexp = (int32_t) precision - exp;
const int32_t requiredTwos = -e2 - rexp;
bool trailingZeros = requiredTwos <= 0
|| (requiredTwos < 60 && multipleOfPowerOf2(m2, (uint32_t) requiredTwos));
if (rexp < 0) {
const int32_t requiredFives = -rexp;
trailingZeros = trailingZeros && multipleOfPowerOf5(m2, (uint32_t) requiredFives);
}
view all matches for this distribution
view release on metacpan or search on metacpan
lua/WalshTransform.lua view on Meta::CPAN
local M = {} -- public interface
M.Version = '1.17'
M.VersionDate = '12aug2010'
-- Example usage:
-- local WT = require 'WalshTransform'
-- H = WT.fht(a)
--------------------- infrastructure ----------------------
local function warn(str)
io.stderr:write(str,'\n')
lua/WalshTransform.lua view on Meta::CPAN
WalshTransform.lua - Fast Hadamard and Walsh Transforms
=head1 SYNOPSIS
local WT = require 'WalshTransform' -- name doesn't matter of course
local f = {1.618, 2.718, 3.142, 4.669} -- must be power-of-two long
local FH1 = WT.fht(f) -- Hadamard transform
local fh1 = WT.fhtinv(FH1)
-- or
local FW2 = WT.fwt(f) -- Walsh transform
view all matches for this distribution
view release on metacpan or search on metacpan
lib/Math/Yapp.pm view on Meta::CPAN
#
if (defined($self->{coeff}[0])) {$self->{coeff}[0] += $added;}
else {$self->{coeff}[0] = $added;}
} # (Just needed to augment the constant term)
else
{ die "Operator += requires a constant or a Yapp polynomial reference";}
# Didn't die - I have a good value to return
#
return ($self); # (Ought to return something)
}
lib/Math/Yapp.pm view on Meta::CPAN
$self->{degree} = $new_degree; # Copy back degree of multiplied target Yapp
@{$self->{coeff}} = @builder; # and copy back array where we carried
# out the multiplication.
} # All done multiplying Yapps; product is in place
else # No more permitted possibilities
{ die "Operator *= requires a constant or a Yapp polynomial reference";}
# Afterthought: I have found that when I multiply two poly's with conjugate
# complex constant terms, the result will include coefficients like like
# (30.00+0.00i); which is a real, of course, but doesn't look that way.
# Here's the fix:
view all matches for this distribution
view release on metacpan or search on metacpan
examples/client.js view on Meta::CPAN
* JSON string '{ "path": "GET:/math/sum", "one": 1, "two": 2 }' to the API.
* The result will be printed to the console.
* Use Ctrl+D to close the console.
*/
var WebSocket = require('ws');
process.stdin.setEncoding('utf8');
var port = process.argv[2] || 8080;
view all matches for this distribution
view release on metacpan or search on metacpan
lib/MediaCloud/JobManager/Worker.pm view on Meta::CPAN
{
# /somewhere/Foo/Bar.pm
# Expect the package to return its name so that we'll know how to call it:
# http://stackoverflow.com/a/9850017/200603
$path_or_name = require $path_or_name;
if ( $path_or_name . '' eq '1' )
{
LOGDIE( "The function package should return __PACKAGE__ at the end of the file instead of just 1." );
}
$path_or_name->import();
view all matches for this distribution
view release on metacpan or search on metacpan
lib/Memcached/libmemcached/API.pm view on Meta::CPAN
libmemcached_constants
libmemcached_tags
);
# load hash of libmemcached functions created by Makefile.PL
my $libmemcached_funcs = require "Memcached/libmemcached/func_hash.pl";
die "Memcached/libmemcached/func_hash.pl failed sanity check"
unless ref $libmemcached_funcs eq 'HASH'
and keys %$libmemcached_funcs > 20;
# extra functions provided by Memcached::libmemcached
lib/Memcached/libmemcached/API.pm view on Meta::CPAN
grep { $funcs{$_} } sort keys %funcs;
};
# load hash of libmemcached functions created by Makefile.PL
my $libmemcached_consts = require "Memcached/libmemcached/const_hash.pl";
die "Memcached/libmemcached/const_hash.pl failed sanity check"
unless ref $libmemcached_consts eq 'HASH'
and keys %$libmemcached_consts > 20;
our @libmemcached_consts = sort keys %$libmemcached_consts;
view all matches for this distribution
view release on metacpan or search on metacpan
; version_rel_day = 22
; version_rel_hour = 5
; version_rel_time_zone = Pacific/Auckland
; 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 all matches for this distribution
view release on metacpan or search on metacpan
; version_rel_day = 22
; version_rel_hour = 5
; version_rel_time_zone = Pacific/Auckland
; 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
[Prereqs]
Moo = 1.000008
[Prereqs / developrequires]
-phase = develop
-relation = requires
MetaPOD::Format::JSON = 0.3.0
view all matches for this distribution
view release on metacpan or search on metacpan
bin/makeMicroarrayDataset.pl view on Meta::CPAN
$0 -file <file/name> -name <intended/dataset/name> [-dataout <repository_directory> -imageout <image directory> -contrast <float> -colorscheme <rg|yb> -corrcutoff <float> -verbose]
-----------------------------------------------------------------------------
-file = required input file (currently only '.cdt' files supported)
-name = required dataset name to be created
(may be delimited by slashes(/) to imply hierarchy)
-rootpath = required root directory, under which must exist html
and data directories
-contrast = optional contrast value for the generated images
(defaults to 4, As the data are expected to be in
log base 2, this corresponds to a 16-fold change as
view all matches for this distribution
view release on metacpan or search on metacpan
; version_rel_day = 31
; version_rel_hour = 6
; version_rel_time_zone = Pacific/Auckland
; 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 all matches for this distribution
view release on metacpan or search on metacpan
; version_rel_month = 3
; version_rel_day = 22
; version_rel_hour = 13
; version_rel_time_zone = Pacific/Auckland
-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 all matches for this distribution
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 all matches for this distribution
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 all matches for this distribution
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 all matches for this distribution
view release on metacpan or search on metacpan
corpus/state_require.pm view on Meta::CPAN
sub do_it {
state $rc = require ConfigReader::Simple;
}
my $rc = require Mojo::Util;
my %data = (
require => 42, # Should not report '=>'.
);
view all matches for this distribution
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 all matches for this distribution
view release on metacpan or search on metacpan
lib/Module/Load/Conditional.pm view on Meta::CPAN
}
}
=back
=head2 @list = requires( MODULE );
C<requires> can tell you what other modules a particular module
requires. This is particularly useful when you're intending to write
a module for public release and are listing its prerequisites.
view all matches for this distribution
view release on metacpan or search on metacpan
share/template/Makefile.PL view on Meta::CPAN
abstract '[% abstract %]';
version '[% version %]';
license '[% license %]';
perl_version '[% perl_version %]';
[% FOR r = requires -%]
[% module = r.keys.0 -%]
requires '[% module %]' => '[% r.$module %]';
[% END -%]
[% IF install_script -%]
view all matches for this distribution
view release on metacpan or search on metacpan
[Prereqs / DevelopRequires]
Test::Builder = 0.90 ; for is_passing
[DynamicPrereqs]
:version = 0.016
-raw = requires('IO::Scalar') if "$]" < '5.008';
view all matches for this distribution
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 all matches for this distribution
view release on metacpan or search on metacpan
lib/Module/Release/VerifyGPGSignature.pm view on Meta::CPAN
=over 4
=cut
sub _get_file_pairs ( $self ) {
state $rc = require Getopt::Long;
my $key = _key($self);
my $string = $self->config->$key();
my( $ret, $args ) = Getopt::Long::GetOptionsFromString($string);
view all matches for this distribution
view release on metacpan or search on metacpan
lib/Module/Release.pm view on Meta::CPAN
Changes file.
=cut
sub get_release_date {
state $rc = require Time::Piece;
return Time::Piece->gmtime->datetime . 'Z';
}
=item run
view all matches for this distribution
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 all matches for this distribution
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 all matches for this distribution
view release on metacpan or search on metacpan
lib/Mojo/Phantom.pm view on Meta::CPAN
has template => <<'TEMPLATE';
% my ($self, $url, $js) = @_;
// Setup perl function
function perl() {
var system = require('system');
var args = Array.prototype.slice.call(arguments);
system.stdout.writeLine(JSON.stringify(args));
system.stdout.writeLine('<%== $self->sep %>');
system.stdout.flush();
}
lib/Mojo/Phantom.pm view on Meta::CPAN
domain: '<%== $cookie->domain || $self->base->host %>',
}) || perl.diag('Failed to import cookie <%== $name %>');
% }
// Requst page and inject user-provided javascript
var page = require('webpage').create();
page.onError = onError;
% if($self->note_console) {
// redirect browser console log to TAP
view all matches for this distribution
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 all matches for this distribution
view release on metacpan or search on metacpan
lib/Mojo/Base/Che.pm view on Meta::CPAN
#~ push @libs, $it # abs lib
#~ and next
#~ if $it =~ m'^/';
#~ $findbin ||= require FindBin && $FindBin::Bin;# relative lib
#~ push @libs, $findbin.'/'.$it;
#~ }
#~ my @ok_libs = grep { my $lib = $_; not scalar grep($lib eq $_, @INC) } @libs
#~ if @libs;
view all matches for this distribution
view release on metacpan or search on metacpan
lib/Mojolicious/Plugin/AssetPack/Pipe/RollupJs.pm view on Meta::CPAN
#!/usr/bin/env node
"use strict"
const globals = __GLOBALS__;
const external = __EXTERNAL__;
const rollup = require("rollup");
const stdout = process.stdout;
function _interopDefault(i) {
return i && typeof i === "object" && "default" in i ? i["default"] : i;
}
view all matches for this distribution