view release on metacpan or search on metacpan
Method/FINDOFF.pm view on Meta::CPAN
=item verbose - If this argument is set to true (1), then this method will
print progress statements. Defaults to false.
This method uses the Starlink FINDOFF task, which is part of
CCDPACK. In order for this method to work it must be able to find
FINDOFF. It first looks in the directory pointed to by the CCDPACK_DIR
environment variable, then it looks in the Starlink binary files
directory pointed to by the Starlink::Config module, with C</ccdpack>
appended. If either of these fail, then this method will croak. See
the C<Starlink::Config> module for information on overriding the base
Starlink directory for non-standard installations.
view release on metacpan or search on metacpan
CheckStatus.pm view on Meta::CPAN
sub STORE
{
require Scalar::Util;
if ( defined $_[1] && ! ref $_[1] && Scalar::Util::looks_like_number( $_[1] ) )
{
# set to non-zero value
if ( $_[0]->{value} = $_[1] )
{
require Astro::FITS::CFITSIO;
view release on metacpan or search on metacpan
lib/Astro/FITS/HdrTrans/CGS4New.pm view on Meta::CPAN
=item B<to_ROTATION>
This determines the angle, in decimal degrees, of the rotation of the
sky component of the WCS. It uses the standard transformation matrix
PCi_j as defined in the FITS WCS Standard. In the absence of a PCi_j
matrix, it looks for the CROTA2 keyword.
For CGS4 the PCi_j matrix is obtained from i=[2,3] and j=[2,3].
=cut
view release on metacpan or search on metacpan
listkids|||
list|||
load_module_nocontext|||vn
load_module|5.006000||pv
localize|||
looks_like_bool|||
looks_like_number|||
lop|||
mPUSHi|5.009002||p
mPUSHn|5.009002||p
mPUSHp|5.009002||p
mPUSHs|5.011000||p
view release on metacpan or search on metacpan
listkids|||
list|||
load_module_nocontext|||vn
load_module|5.006000||pv
localize|||
looks_like_bool|||
looks_like_number|||
lop|||
mPUSHi|5.009002||p
mPUSHn|5.009002||p
mPUSHp|5.009002||p
mPUSHs|5.011000||p
view release on metacpan or search on metacpan
lib/Astro/NED/Query.pm view on Meta::CPAN
# map between Multiple values and form inputs.
# HTML::Table creates a separate input for each value in a checkbox
# or option. this routine creates a hash matching the values to the
# input to make it easier to set the inputs. In some cases a single
# logical list of options is split into several so the GUI looks
# cleaner. this will merge them.
sub _setupMultiple
{
my ( $self, $type, $alias, @names ) = @_;
view release on metacpan or search on metacpan
libnova-0.15.0/INSTALL view on Meta::CPAN
================
If you want to set default values for `configure' scripts to share,
you can create a site shell script called `config.site' that gives
default values for variables like `CC', `cache_file', and `prefix'.
`configure' looks for `PREFIX/share/config.site' if it exists, then
`PREFIX/etc/config.site' if it exists. Or, you can set the
`CONFIG_SITE' environment variable to the location of the site script.
A warning: not all `configure' scripts look for a site script.
Operation Controls
view release on metacpan or search on metacpan
lib/Astro/PAL.pm view on Meta::CPAN
=item palObs
palObs is special in that it returns an empty list if the return
status is bad. Additionally, palObs is called with a single
argument and the behaviour depends on whether the argument looks
like an integer or a string.
($ident, $name, $w, $p, $h) = palObs( 27 );
($ident, $name, $w, $p, $h) = palObs( "JCMT" );
view release on metacpan or search on metacpan
inc/My/Module/Test.pm view on Meta::CPAN
C<call()>, C<count()>, C<deref()>, C<deref_curr()>, or C<find()> is
compared to the expected value, and the test succeeds or fails based on
the result of the comparison.
If the expected value is a C<Regexp> object, the comparison is done with
the C<Test::More> C<like()> subroutine. If it looks like a number, the
comparison is done with C<cmp_ok> for numeric equality. Otherwise, the
comparison is done with C<is>.
=head1 SUPPORT
view release on metacpan or search on metacpan
inc/Devel/CheckLib.pm view on Meta::CPAN
It works by trying to compile some code - which defaults to this:
int main(void) { return 0; }
and linking it to the specified libraries. If something pops out the end
which looks executable, it gets executed, and if main() returns 0 we know
that it worked. That tiny program is
built once for each library that you specify, and (without linking) once
for each header file.
If you want to check for the presence of particular functions in a
view release on metacpan or search on metacpan
lib/Astro/SkyX/AutomatedImageLinkSettings.pm view on Meta::CPAN
use Astro::SkyX;
blah blah blah
=head1 DESCRIPTION
Stub documentation for SkyX, created by h2xs. It looks like the
author of the extension was negligent enough to leave the stub
unedited.
Blah blah blah.
view release on metacpan or search on metacpan
lib/Astro/SpaceTrack.pm view on Meta::CPAN
The argument specifies a special data set.
=back
The default is C<'CATNR'> if the argument is numeric, C<'INTDES'> if the
argument looks like an international designator, or C<'GROUP'>
otherwise.
=back
A list of valid C<GROUP> names and brief descriptions can be obtained by
lib/Astro/SpaceTrack.pm view on Meta::CPAN
The argument specifies a special data set.
=back
The default is C<'CATNR'> if the argument is numeric, C<'INTDES'> if the
argument looks like an international designator, or C<'FILE'> otherwise.
=item rms
This Boolean option specifies that RMS data be returned rather than TLE
data, if available. This option is valid only on known catalogs that
lib/Astro/SpaceTrack.pm view on Meta::CPAN
return $resp;
}
# FIXME in the last couple days this has started returning nothing.
# It looks like -exclude debris excludes everything, as does
# -exclude rocket.
# Get Iridium status from Space Track. Unlike the other sources,
# Space Track does not know whether satellites are in service or
# not, but it does know about all of them, and whether or not they
lib/Astro/SpaceTrack.pm view on Meta::CPAN
$context->{data} = $content;
}
return;
}
# _check_cookie_generic looks for our session cookie. If it is found, it
# returns true if it thinks the cookie is valid, and false otherwise. If
# it is not found, it returns false.
sub _record_cookie_generic {
my ( $self, $version ) = @_;
lib/Astro/SpaceTrack.pm view on Meta::CPAN
# _dump_cookie is intended to be called from inside the
# HTTP::Cookie->scan method. The first argument is prefix text
# for the dump, and the subsequent arguments are the arguments
# passed to the scan method.
# It dumps the contents of the cookie to STDERR via a warn ().
# A typical session cookie looks like this:
# version => 0
# key => 'spacetrack_session'
# val => whatever
# path => '/'
# domain => 'www.space-track.org'
lib/Astro/SpaceTrack.pm view on Meta::CPAN
}
}
# $opt = _parse_retrieve_dates ($opt);
# This subroutine looks for keys start_epoch and end_epoch in the
# given option hash, parses them as YYYY-MM-DD (where the letters
# are digits and the dashes are any non-digit punctuation), and
# replaces those keys' values with a reference to a list
# containing the output of timegm() for the given time. If only
# one epoch is provided, the other is defaulted to provide a
view release on metacpan or search on metacpan
standard version tags to 1.1x and HTN/0.2 repsectively. Removed
<WhereWhen type="stc"> tag to make the messages validate!
2005-12-28 Alasdair Allan <aa@astro.ex.ac.uk>
* VOEvent.pm: modifed time() method so it looks in <Who> if there
isn't a valid datestamp in the <WhereWhen> tag.
2005-12-19 Alasdair Allan <aa@astro.ex.ac.uk>
* VOEvent.pm: Fixed casing problem for <WhereWhen type="simple">,
view release on metacpan or search on metacpan
=back
=head1 BUGS
Likely many! Very little of the module has been tested. If you find
something that looks like a bug, please send a report.
=head1 AUTHOR
Pete Ratzlaff <pratzlaff@cfa.harvard.edu>
view release on metacpan or search on metacpan
inc/My/Module/Meta.pm view on Meta::CPAN
'Clone' => 0,
'Data::Dumper' => 0,
'Exporter' => 5.64,
'IO::File' => 0,
'POSIX' => 0,
'Scalar::Util' => 1.22, # For looks_like_number
'Time::Local' => 0,
base => 0,
constant => 0,
if => 0,
strict => 0,
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/Async/Queue.pm view on Meta::CPAN
use 5.006;
use strict;
use warnings;
use Carp;
use Scalar::Util qw(looks_like_number);
sub new {
my ($class, %options) = @_;
my $self = bless {
concurrency => 1,
lib/Async/Queue.pm view on Meta::CPAN
sub concurrency {
my ($self, $conc) = @_;
if(@_ > 1) {
croak "You cannot set concurrency while there is a running task" if $self->running > 0;
$conc = 1 if not defined($conc);
croak "concurrency must be a number" if !looks_like_number($conc);
$self->{concurrency} = int($conc);
}
return $self->{concurrency};
}
view release on metacpan or search on metacpan
examples/stress/README.md view on Meta::CPAN
- `2` hang (a workload future did not unwind within `--command-deadline`).
- `3` configuration error.
## Interpreting output
Each JSONL record looks like:
```
{"kind": "metric", "t": 1761350400.123, "elapsed_s": 42.5,
"throughput": {"get": 4231, "set": 3899},
"latency_ms": {"get": {"p50": 0.4, "p95": 1.2, "p99": 4.8}},
view release on metacpan or search on metacpan
src/ppport.h view on Meta::CPAN
listkids|||
list|||
load_module_nocontext|||vn
load_module|5.006000||pv
localize|||
looks_like_bool|||
looks_like_number|||
lop|||
mPUSHi|5.009002||p
mPUSHn|5.009002||p
mPUSHp|5.009002||p
mPUSHs|5.010001||p
view release on metacpan or search on metacpan
When you call a method like C<app.bsky.actor.getProfile>, the library:
=over
=item 1. B<Checks user-provided paths:> It looks in any directories passed to C<lexicon_paths>.
=item 2. B<Checks local storage:> It looks for the schema in the distribution's C<share> directory.
=item 3. B<Checks user cache:> It looks in C<~/.cache/atproto/lexicons/>.
=item 4. B<Downloads if missing:> If not found, it automatically downloads the schema from the
official AT Protocol repository and saves it to your user cache.
=back
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
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
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
(define add (lambda (a) (lambda (b) (+ a b))))
(define add2 (add 2))
(map add2 (list 1 2 3))
;; => (list 3 4 5)
Using C<Attribute::Curried>, the Perl equivalent looks like this:
sub add :Curry(2) { $_[0] + $_[1] }
*add2 = add(2);
map { add2($_) } 1..3;
# => (3, 4, 5)
view release on metacpan or search on metacpan
lib/Attribute/GlobalEnable.pm view on Meta::CPAN
{ Attribute_name => [ list of flags ], Attribute_name_2 ... }
The ENABLE_FLAG is optional, and describes flags that can be set for the
exported 'Attribute_name' subroutines. These are exported as global
constants, so it looks nice and neat in your code. This essentially links
that sub call to that flag. The flag is still set like it would normally be
set in the ENABLE_CHK hash, however, you still must use the 'SPECIAL_KEY'
(see above) in the assignment, so your assignment will look like:
'SPECIAL_KEY'_'FLAG'
view release on metacpan or search on metacpan
lib/Attribute/Handlers.pm view on Meta::CPAN
non-array-reference arguments in an array constructor:
$data = [ $data ] unless ref $data eq 'ARRAY';
Typically, however, things are the other way around: the tieable class expects
its arguments as a flattened list, so the attribute looks like:
sub UNIVERSAL::Cycle : ATTR(SCALAR) {
my ($package, $symbol, $referent, $attr, $data, $phase) = @_;
my @data = ref $data eq 'ARRAY' ? @$data : $data;
tie $$referent, 'Tie::Whatever', @data;
lib/Attribute/Handlers.pm view on Meta::CPAN
=item findsym
my $symbol = Attribute::Handlers::findsym($package, $referent);
The function looks in the symbol table of C<$package> for the typeglob for
C<$referent>, which is a reference to a variable or subroutine (SCALAR, ARRAY,
HASH, or CODE). If it finds the typeglob, it returns it. Otherwise, it returns
undef. Note that C<findsym> memoizes the typeglobs it has previously
successfully found, so subsequent calls with the same arguments should be
much faster.