view release on metacpan or search on metacpan
return sprintf($format, $t/(86400 * 365.25)) . " years";
}
# Considered, but removed, months entries in seconds_for_display()
# 1) hard to abbreviate months in 4 chars. mnths?
# 2) 2.1 months looks especially weird
# 3) months are much more variable-sized than any other time unit
# therefore more ambiguous and complex to compute (Ie, 28 vs 31 days)
#my $seconds_per_month = (365.25 / 12) * 86400; # mythical equal-sized months
#if (abs($t) >= $seconds_per_month) {
# return sprintf($format, $t/$seconds_per_month) . " mnths";
view release on metacpan or search on metacpan
bin/prereq-grapher view on Meta::CPAN
-verbose Display verbose messages as we run
-h --help This help
=head1 DESCRIPTION
B<prereq-grapher> parses perl source and looks for prerequisites,
such as modules that are C<use>'d or C<require>'d.
All of those modules are then parsed in turn,
looking for I<their> dependencies.
Once all files have been parsed, B<prereq-grapher> will write out
view release on metacpan or search on metacpan
bin/prima-repl view on Meta::CPAN
#sub allow_lexicals { $lexicals_allowed = 1 };
else {
# A command to be eval'd. Lexical variables don't work, so croak if I
# see one. This could probably be handled better.
if ($in_text =~ /my/ and not $lexicals_allowed) {
$@ = join(' ', 'It looks to me like you\'re trying to use a lexical variable.'
, 'Lexical variables not allowed in the line evaluator'
, 'because you cannot get to them after the current line.'
, 'If I\'m wrong, or if you really want to use lexical variables,'
, "do this:\n"
, " allow_lexicals; <command-here>"
view release on metacpan or search on metacpan
Force pipe mode.
=item -l, --log=FILENAME
Log filtered output to FILENAME. If the argument looks like a pathname
(contains a "/"), we'll use that. Otherwise, the output will go to the
temporary directory (as defined by File::Spec->tmpdir).
The special value "auto" lets prolix pick a filename based on the command
being run.
view release on metacpan or search on metacpan
inc/Module/Install.pm view on Meta::CPAN
if ( my $code = $sym->{$pwd} ) {
# Delegate back to parent dirs
goto &$code unless $cwd eq $pwd;
}
unless ($$sym =~ s/([^:]+)$//) {
# XXX: it looks like we can't retrieve the missing function
# via $$sym (usually $main::AUTOLOAD) in this case.
# I'm still wondering if we should slurp Makefile.PL to
# get some context or not ...
my ($package, $file, $line) = caller;
die <<"EOT";
view release on metacpan or search on metacpan
inc/Module/Install.pm view on Meta::CPAN
if ( my $code = $sym->{$pwd} ) {
# Delegate back to parent dirs
goto &$code unless $cwd eq $pwd;
}
unless ($$sym =~ s/([^:]+)$//) {
# XXX: it looks like we can't retrieve the missing function
# via $$sym (usually $main::AUTOLOAD) in this case.
# I'm still wondering if we should slurp Makefile.PL to
# get some context or not ...
my ($package, $file, $line) = caller;
die <<"EOT";
view release on metacpan or search on metacpan
inc/Module/Install.pm view on Meta::CPAN
if ( my $code = $sym->{$pwd} ) {
# Delegate back to parent dirs
goto &$code unless $cwd eq $pwd;
}
unless ($$sym =~ s/([^:]+)$//) {
# XXX: it looks like we can't retrieve the missing function
# via $$sym (usually $main::AUTOLOAD) in this case.
# I'm still wondering if we should slurp Makefile.PL to
# get some context or not ...
my ($package, $file, $line) = caller;
die <<"EOT";
view release on metacpan or search on metacpan
lib/App/Puppet/Environment/Updater.pm view on Meta::CPAN
necessary to use Git submodules, but it simplifies reuse of the Puppet modules in
other projects.
=back
The sandbox of the Git repository usually looks about as follows:
.
|-- modules
| |-- module1
| | |-- manifests
view release on metacpan or search on metacpan
inc/Module/Install.pm view on Meta::CPAN
if ( my $code = $sym->{$pwd} ) {
# Delegate back to parent dirs
goto &$code unless $cwd eq $pwd;
}
unless ($$sym =~ s/([^:]+)$//) {
# XXX: it looks like we can't retrieve the missing function
# via $$sym (usually $main::AUTOLOAD) in this case.
# I'm still wondering if we should slurp Makefile.PL to
# get some context or not ...
my ($package, $file, $line) = caller;
die <<"EOT";
view release on metacpan or search on metacpan
public/js/flot.js view on Meta::CPAN
return layer;
};
// Creates (if necessary) and returns a text info object.
//
// The object looks like this:
//
// {
// width: Width of the text's wrapper div.
// height: Height of the text's wrapper div.
// element: The jQuery-wrapped HTML div containing the text.
public/js/flot.js view on Meta::CPAN
}
function allocateAxisBoxFirstPhase(axis) {
// find the bounding box of the axis by looking at label
// widths/heights and ticks, make room by diminishing the
// plotOffset; this first phase only looks at one
// dimension per axis, the other dimension depends on the
// other axes so will have to wait
var lw = axis.labelWidth,
lh = axis.labelHeight,
view release on metacpan or search on metacpan
inc/Module/Install.pm view on Meta::CPAN
if ( my $code = $sym->{$pwd} ) {
# Delegate back to parent dirs
goto &$code unless $cwd eq $pwd;
}
unless ($$sym =~ s/([^:]+)$//) {
# XXX: it looks like we can't retrieve the missing function
# via $$sym (usually $main::AUTOLOAD) in this case.
# I'm still wondering if we should slurp Makefile.PL to
# get some context or not ...
my ($package, $file, $line) = caller;
die <<"EOT";
view release on metacpan or search on metacpan
lib/App/Raps2/UI.pm view on Meta::CPAN
Returns a new App::Raps2::UI object.
=item $ui->list(I<\@item1>, I<\@item2>, I<\@item3>)
Print the list items neatly formatted to stdout. Each I<item> looks like B<[>
I<key>, I<value> B<]>. When B<list> is called for the first time, it will
print the keys as well as the values.
=item $ui->read_line(I<$question>, [I<$prefill>])
view release on metacpan or search on metacpan
lib/App/RecordStream.pm view on Meta::CPAN
cpanm --interactive App::RecordStream
Using L<cpanm> in interactive mode will prompt you for optional feature
support. Other CPAN clients such as L<cpan> and L<cpanp> also work fine, but
you can't opt to use any optional features (just like cpanm in non-interactive
mode). A kitchen-sink install of App::RecordStream looks like:
cpanm --with-recommends --with-all-features App::RecordStream
If you don't have L<cpanm> itself, you can install it easily with:
view release on metacpan or search on metacpan
lib/App/Regather/Plugin.pm view on Meta::CPAN
cf reference to Config class object
force force all actions done on start
log reference to Logg class object
obj reference to Net::LDAP object
out_file_old ... looks like it is not needed any more ...
prog program name and version
rdn RDN of a LDAP object event relates to
s service
st syncrepl state
ts_fmt timestamp format
view release on metacpan or search on metacpan
t/dat/lib/Nada.pm view on Meta::CPAN
=head1 DESCRIPTION
Stub documentation for Nada,
created by perlnow.el using template.el.
It looks like the author of the extension was negligent
enough to leave the stub unedited.
Blah blah blah.
=head2 EXPORT
view release on metacpan or search on metacpan
inc/Module/Install.pm view on Meta::CPAN
if ( my $code = $sym->{$pwd} ) {
# Delegate back to parent dirs
goto &$code unless $cwd eq $pwd;
}
unless ($$sym =~ s/([^:]+)$//) {
# XXX: it looks like we can't retrieve the missing function
# via $$sym (usually $main::AUTOLOAD) in this case.
# I'm still wondering if we should slurp Makefile.PL to
# get some context or not ...
my ($package, $file, $line) = caller;
die <<"EOT";
view release on metacpan or search on metacpan
lib/App/Repository.pm view on Meta::CPAN
$context = App->context();
$repository = $context->service("Repository"); # or ...
$repository = $context->repository();
$rep = Repository::Base->new(); # looks for %ENV, then config file
$rep = Repository::Base->new("sysdb"); # looks for %ENV, then config file using "sysdb"
$rep2 = $rep->new(); # copies attributes of existing $rep
$rep = Repository::Base->new(@positional_args); # undefined for Repository::Base
$config = {
'repository' => {
'db' => {
view release on metacpan or search on metacpan
lib/App/Requirement/Arch.pm view on Meta::CPAN
The requirement format is defined in I<master_template.pl>. The template is used to create new requirements and check existing templates.
I<master_template.pl> also contains the definition of a use case template. It is possible to modify and expand I<master_template.pl> with
more type or different fields for a type. The discussion below is not about the individual fields but their format, see L<Default template fields>.
for the REQUIREMENT type the template looks like:
{
UUID => {TYPE =>$SCALAR, DEFAULT => undef},
TYPE => {TYPE =>$SCALAR, DEFAULT => 'requirement', ACCEPTED_VALUES => ['use case', 'requirement']},
ABSTRACTION_LEVEL => {TYPE =>$SCALAR, DEFAULT => 'system', ACCEPTED_VALUES => ['architecture', 'system', 'module', 'none'], OPTIONAL => 1},
view release on metacpan or search on metacpan
lib/App/ReslirpTunnel.pm view on Meta::CPAN
sub _autodetect_remote_os {
my $self = shift;
my $ssh = $self->{ssh};
my $out = $ssh->capture('echo %COMSPEC%');
my $looks_like_unix = $out =~ /^\%COMSPEC\%$/m;
if ($looks_like_unix) {
$self->_log(debug => "Looks like a Unix-like system, let's check it further...");
my $uname = lc $ssh->capture('uname -s');
if ($uname =~ /^(Linux|Darwin|FreeBSD|OpenBSD|NetBSD|DragonFly|MidnightBSD|AIX|HP-UX|SunOS|IRIX|OSF1|SCO_SV|QNX)$/i) {
$self->_log(info => "Remote OS identified as Linux/UNIX ($1)");
return 'unix';
view release on metacpan or search on metacpan
lib/App/Ringleader.pm view on Meta::CPAN
applications, you probably want to define your services using
L<Ubic::Service::Plack>.
=head1 CONFIGURATION FILE
The Ringleader configuration file is YAML-based, and looks like
port: 3000
inactivity_delay: 60
services:
techblog.babyl.ca: webapp.techblog
view release on metacpan or search on metacpan
lib/App/RoboBot/Message.pm view on Meta::CPAN
if ($self->raw =~ m{^\!+((\S+).*)}) {
$self->log->debug(sprintf('Legacy bang syntax detected in message on network %s. Rewriting as an expression.', $self->network->name));
my ($no_excl, $maybe_cmd) = ($1, $2);
# If there is at least one pipe character followed by what looks to
# be possibly another command, treat the incoming message as if it
# is the old-style piped command chain, and convert to nested
# expressions.
if ($no_excl =~ m{\|\s+\!\S+}) {
my @chained = split(/\|/, $no_excl);
lib/App/RoboBot/Message.pm view on Meta::CPAN
|| exists $self->bot->macros->{$self->network->id}{lc($maybe_cmd)};
}
} elsif ($self->raw =~ m{ ^ $self->bot->nick->name : \s* (.+) }ixs) {
$self->log->debug(sprintf('Incoming message on network %s was addressed to the bot. Stripping bot name and treating as expression.', $self->network->name));
# It looks like someone said something to us directly, so strip off our
# nick from the front, and treat the reast as if it were a command.
$self->raw('('.$1.')');
}
if ($self->raw =~ m{^\s*\(\S+}o) {
$self->log->debug(sprintf('Incoming message on network %s looks like an expression. Attempting to parse.', $self->network->name));
my $parser = App::RoboBot::Parser->new( bot => $self->bot );
my $expr;
eval {
view release on metacpan or search on metacpan
lib/App/Rssfilter/Match/BbcSports.pm view on Meta::CPAN
=head2 match
my $item_is_BBC_sport = App::Rssfilter::Match::BbcSports::match( $item );
Returns true if ther GUID of C<$item> looks like a BBC sport GUID (like C<http://www.bbc.co.uk/sport>).
=head1 SEE ALSO
=over 4
view release on metacpan or search on metacpan
inc/Module/Install.pm view on Meta::CPAN
if ( my $code = $sym->{$pwd} ) {
# Delegate back to parent dirs
goto &$code unless $cwd eq $pwd;
}
unless ($$sym =~ s/([^:]+)$//) {
# XXX: it looks like we can't retrieve the missing function
# via $$sym (usually $main::AUTOLOAD) in this case.
# I'm still wondering if we should slurp Makefile.PL to
# get some context or not ...
my ($package, $file, $line) = caller;
die <<"EOT";
view release on metacpan or search on metacpan
inc/Module/Install.pm view on Meta::CPAN
if ( my $code = $sym->{$pwd} ) {
# Delegate back to parent dirs
goto &$code unless $cwd eq $pwd;
}
unless ($$sym =~ s/([^:]+)$//) {
# XXX: it looks like we can't retrieve the missing function
# via $$sym (usually $main::AUTOLOAD) in this case.
# I'm still wondering if we should slurp Makefile.PL to
# get some context or not ...
my ($package, $file, $line) = caller;
die <<"EOT";
view release on metacpan or search on metacpan
lib/App/SVN/Bisect.pm view on Meta::CPAN
END
'view' => <<"END",
Usage: $0 view
Outputs some descriptive information about where we're at, and about
the revisions remaining to be tested. The output looks like:
There are currently 7 revisions under scrutiny.
The last known-unaffected rev is 28913.
The first known- affected rev is 28928.
Currently testing 28924.
view release on metacpan or search on metacpan
lib/App/Sandy/DB/Handle/Expression.pm view on Meta::CPAN
use App::Sandy::Base 'class';
use App::Sandy::DB;
use IO::Compress::Gzip 'gzip';
use IO::Uncompress::Gunzip 'gunzip';
use Storable qw/nfreeze thaw/;
use Scalar::Util 'looks_like_number';
with 'App::Sandy::Role::IO';
our $VERSION = '0.25'; # VERSION
lib/App/Sandy/DB/Handle/Expression.pm view on Meta::CPAN
die "Error parsing expression-matrix '$file': Seqid (first column) not found at line $line\n"
unless defined $fields[0];
die "Error parsing expression-matrix '$file': Count (second column) not found at line $line\n"
unless defined $fields[1];
die "Error parsing expression-matrix '$file': Count (second column) does not look like a number at line $line\n"
if not looks_like_number($fields[1]);
# Only throws a warning, because it is common zero values in expression matrix
if ($fields[1] <= 0) {
log_msg ":: Parsing expression-matrix '$file': Ignoring seqid '$fields[0]': Count (second column) lesser or equal to zero at line $line\n";
next;
view release on metacpan or search on metacpan
inc/Module/Install.pm view on Meta::CPAN
if ( my $code = $sym->{$pwd} ) {
# Delegate back to parent dirs
goto &$code unless $cwd eq $pwd;
}
unless ($$sym =~ s/([^:]+)$//) {
# XXX: it looks like we can't retrieve the missing function
# via $$sym (usually $main::AUTOLOAD) in this case.
# I'm still wondering if we should slurp Makefile.PL to
# get some context or not ...
my ($package, $file, $line) = caller;
die <<"EOT";
view release on metacpan or search on metacpan
inc/Module/Install.pm view on Meta::CPAN
if ( my $code = $sym->{$pwd} ) {
# Delegate back to parent dirs
goto &$code unless $cwd eq $pwd;
}
unless ($$sym =~ s/([^:]+)$//) {
# XXX: it looks like we can't retrieve the missing function
# via $$sym (usually $main::AUTOLOAD) in this case.
# I'm still wondering if we should slurp Makefile.PL to
# get some context or not ...
my ($package, $file, $line) = caller;
die <<"EOT";
view release on metacpan or search on metacpan
lib/App/Scheme79asm.pm view on Meta::CPAN
use re '/s';
use Carp qw/croak/;
use Data::Dumper qw/Dumper/;
use Data::SExpression qw/consp scalarp/;
use Scalar::Util qw/looks_like_number/;
our $VERSION = '1.000';
our %TYPES = (
LIST => 0,
lib/App/Scheme79asm.pm view on Meta::CPAN
}
$addr = $self->process($addr) if ref $addr eq 'ARRAY';
die 'Addr of toplevel is not atom: ', Dumper($addr), "\n" unless scalarp($addr);
my ($comment_type, $comment_addr) = ($type, $addr);
die 'Computed addr is not a number: ', Dumper($addr), "\n" unless looks_like_number $addr;
if (!looks_like_number $type) {
die "No such type: $type\n" unless exists $TYPES{$type};
$type = $TYPES{$type};
}
$addr += (1 << $self->{addr_bits}) if $addr < 0;
view release on metacpan or search on metacpan
script/set-screensaver-timeout view on Meta::CPAN
Not yet supported.
=item * KDE
To set timeout for the KDE screen locker, the program looks for this line in
C<~/.kde/share/config/kscreensaverrc>:
Timeout=300
modifies the line, save the file.