view release on metacpan or search on metacpan
If you develop a new program, and you want it to be of the greatest
possible use to humanity, the best way to achieve this is to make it
free software which everyone can redistribute and change under these
terms.
To do so, attach the following notices to the program. It is safest to
attach them to the start of each source file to most effectively convey
the exclusion of warranty; and each file should have at least the
"copyright" line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) 19yy <name of author>
view all matches for this distribution
view release on metacpan or search on metacpan
If you develop a new program, and you want it to be of the greatest
possible use to humanity, the best way to achieve this is to make it
free software which everyone can redistribute and change under these
terms.
To do so, attach the following notices to the program. It is safest to
attach them to the start of each source file to most effectively convey
the exclusion of warranty; and each file should have at least the
"copyright" line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) 19yy <name of author>
view all matches for this distribution
view release on metacpan or search on metacpan
If you develop a new program, and you want it to be of the greatest
possible use to humanity, the best way to achieve this is to make it
free software which everyone can redistribute and change under these
terms.
To do so, attach the following notices to the program. It is safest to
attach them to the start of each source file to most effectively convey
the exclusion of warranty; and each file should have at least the
"copyright" line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) 19yy <name of author>
view all matches for this distribution
view release on metacpan or search on metacpan
lib/CWB/CEQL/Parser.pm view on Meta::CPAN
The example below extends our simple query language with regexp-style
parenthesised groups, quantifiers (C<?>, C<*>, C<+>) and alternatives (C<|>).
In order to simplify the implementation, metacharacters must be separated from
wordform patterns and from other metacharacters by blanks; and quantifiers
must be attached directly to a closing parenthesis (otherwise, the question
mark in C<) ?> would be ambiguous between a quantifier and a wildcard pattern
matching a single character). Note that the C<simple_query> rule is
practically identical to C<wordform_sequence> above, but has been renamed to
reflect its new semantics.
view all matches for this distribution
view release on metacpan or search on metacpan
If you develop a new program, and you want it to be of the greatest
possible use to humanity, the best way to achieve this is to make it
free software which everyone can redistribute and change under these
terms.
To do so, attach the following notices to the program. It is safest to
attach them to the start of each source file to most effectively convey
the exclusion of warranty; and each file should have at least the
"copyright" line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) 19yy <name of author>
view all matches for this distribution
view release on metacpan or search on metacpan
If you develop a new program, and you want it to be of the greatest
possible use to humanity, the best way to achieve this is to make it
free software which everyone can redistribute and change under these
terms.
To do so, attach the following notices to the program. It is safest to
attach them to the start of each source file to most effectively convey
the exclusion of warranty; and each file should have at least the
"copyright" line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) 19yy <name of author>
view all matches for this distribution
view release on metacpan or search on metacpan
If you develop a new program, and you want it to be of the greatest
possible use to humanity, the best way to achieve this is to make it
free software which everyone can redistribute and change under these
terms.
To do so, attach the following notices to the program. It is safest to
attach them to the start of each source file to most effectively convey
the exclusion of warranty; and each file should have at least the
"copyright" line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) 19yy <name of author>
view all matches for this distribution
view release on metacpan or search on metacpan
If you develop a new program, and you want it to be of the greatest
possible use to humanity, the best way to achieve this is to make it
free software which everyone can redistribute and change under these
terms.
To do so, attach the following notices to the program. It is safest to
attach them to the start of each source file to most effectively convey
the exclusion of warranty; and each file should have at least the
"copyright" line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) 19yy <name of author>
view all matches for this distribution
view release on metacpan or search on metacpan
lib/Devel/CallParser.pm view on Meta::CPAN
=head1 NAME
Devel::CallParser - custom parsing attached to subroutines
=head1 SYNOPSIS
# to generate header prior to XS compilation
lib/Devel/CallParser.pm view on Meta::CPAN
=head1 DESCRIPTION
This module provides a C API, for XS modules, concerned with custom
parsing. It is centred around the function C<cv_set_call_parser>, which
allows XS code to attach a magical annotation to a Perl subroutine,
resulting in resolvable calls to that subroutine having their arguments
parsed by arbitrary C code. (This is a more conveniently structured
facility than the core's C<PL_keyword_plugin> API.) This module makes
C<cv_set_call_parser> and several supporting functions available.
lib/Devel/CallParser.pm view on Meta::CPAN
L<Devel::Declare> prior to 0.006004 and versions of L<Data::Alias> prior
to 1.13. An arrangement has been reached that allows later versions of
those modules to coexist with this module.
Custom parsing code is only invoked if the subroutine to which it is
attached is invoked using an unqualified name. For example, the name
C<foo> works, but the name C<main::foo> will not, despite referring
to the same subroutine. This is an unavoidable limitation imposed by
the core's interim facility for custom parser plugins. This should
be resolved if the API provided by this module, or something similar,
migrates into the core in a future version of Perl.
view all matches for this distribution
view release on metacpan or search on metacpan
inc/Inline.pm view on Meta::CPAN
When the program finishes please bundle up the above build directory with:
tar czf Inline.REPORTBUG.tar.gz $o->{API}{build_dir}
and send "Inline.REPORTBUG.tar.gz" as an email attachment to the author
of the offending Inline::* module with the subject line:
REPORTBUG: Inline.pm
Include in the email, a description of the problem and anything else that
view all matches for this distribution
view release on metacpan or search on metacpan
If you develop a new program, and you want it to be of the greatest
possible use to humanity, the best way to achieve this is to make it
free software which everyone can redistribute and change under these
terms.
To do so, attach the following notices to the program. It is safest to
attach them to the start of each source file to most effectively convey
the exclusion of warranty; and each file should have at least the
"copyright" line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) 19yy <name of author>
view all matches for this distribution
view release on metacpan or search on metacpan
lib/Alt/FFI/Raw/Platypus.pm view on Meta::CPAN
L<FFI::Raw> code without changing any code!
This implementation uses L<FFI::Platypus::Legacy::Raw> which is a fork of the
original L<FFI::Raw> that lives in its own namespace. The former is useful when
you want to migrate to Platypus from Raw to take advantage of its type system
and ability to attach xsubs, but do not want to change all of your code all at
once.
=head1 SEE ALSO
=over 4
view all matches for this distribution
view release on metacpan or search on metacpan
lib/Alt/FFI/libffi.pm view on Meta::CPAN
env PERL_ALT_INSTALL=OVERWRITE cpanm Alt::FFI::libffi
=head1 CAVEATS
The connecting code is all pure perl, and not especially fast. You will likely get
better performance porting your code to L<FFI::Platypus>. When using the C<attach> feature
of L<FFI::Platypus>, it will likely be faster than the original L<FFI> implementation.
=head1 SEE ALSO
=over 4
view all matches for this distribution
view release on metacpan or search on metacpan
If you develop a new program, and you want it to be of the greatest
possible use to humanity, the best way to achieve this is to make it
free software which everyone can redistribute and change under these
terms.
To do so, attach the following notices to the program. It is safest to
attach them to the start of each source file to most effectively convey
the exclusion of warranty; and each file should have at least the
"copyright" line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) 19yy <name of author>
view all matches for this distribution
view release on metacpan or search on metacpan
If you develop a new program, and you want it to be of the greatest
possible use to humanity, the best way to achieve this is to make it
free software which everyone can redistribute and change under these
terms.
To do so, attach the following notices to the program. It is safest to
attach them to the start of each source file to most effectively convey
the exclusion of warranty; and each file should have at least the
"copyright" line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) 19yy <name of author>
view all matches for this distribution
view release on metacpan or search on metacpan
inc/Inline.pm view on Meta::CPAN
When the program finishes please bundle up the above build directory with:
tar czf Inline.REPORTBUG.tar.gz $o->{API}{build_dir}
and send "Inline.REPORTBUG.tar.gz" as an email attachment to the author
of the offending Inline::* module with the subject line:
REPORTBUG: Inline.pm
Include in the email, a description of the problem and anything else that
view all matches for this distribution
view release on metacpan or search on metacpan
If you develop a new program, and you want it to be of the greatest
possible use to humanity, the best way to achieve this is to make it
free software which everyone can redistribute and change under these
terms.
To do so, attach the following notices to the program. It is safest to
attach them to the start of each source file to most effectively convey
the exclusion of warranty; and each file should have at least the
"copyright" line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) 19yy <name of author>
view all matches for this distribution
view release on metacpan or search on metacpan
lib/NewRelic/Agent/FFI/Procedural.pm view on Meta::CPAN
function, not the function itself. You can, however, call it via L<FFI::Platypus>:
use FFI::Platypus;
my $ffi = FFI::Platypus->new;
$new->attach( newrelic_basic_literal_replacement_obfuscator, ['string'] => 'string');
my $save = newrelic_basic_literal_replacement_obfuscator("SELECT * FROM user WHERE password = 'secret'");
=head2 newrelic_request_shutdown
my $rc = newrelic_request_shutdown $reason;
view all matches for this distribution
view release on metacpan or search on metacpan
If you develop a new program, and you want it to be of the greatest
possible use to humanity, the best way to achieve this is to make it
free software which everyone can redistribute and change under these
terms.
To do so, attach the following notices to the program. It is safest to
attach them to the start of each source file to most effectively convey
the exclusion of warranty; and each file should have at least the
"copyright" line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) 19yy <name of author>
view all matches for this distribution
view release on metacpan or search on metacpan
If you develop a new program, and you want it to be of the greatest
possible use to humanity, the best way to achieve this is to make it
free software which everyone can redistribute and change under these
terms.
To do so, attach the following notices to the program. It is safest to
attach them to the start of each source file to most effectively convey
the exclusion of warranty; and each file should have at least the
"copyright" line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) 19yy <name of author>
view all matches for this distribution
view release on metacpan or search on metacpan
If you develop a new program, and you want it to be of the greatest
possible use to humanity, the best way to achieve this is to make it
free software which everyone can redistribute and change under these
terms.
To do so, attach the following notices to the program. It is safest to
attach them to the start of each source file to most effectively convey
the exclusion of warranty; and each file should have at least the
"copyright" line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) 19yy <name of author>
view all matches for this distribution
view release on metacpan or search on metacpan
If you develop a new program, and you want it to be of the greatest
possible use to humanity, the best way to achieve this is to make it
free software which everyone can redistribute and change under these
terms.
To do so, attach the following notices to the program. It is safest to
attach them to the start of each source file to most effectively convey
the exclusion of warranty; and each file should have at least the
"copyright" line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) 19yy <name of author>
view all matches for this distribution
view release on metacpan or search on metacpan
CONTRIBUTING view on Meta::CPAN
not, then try <https://github.com/tobyink> or submit a bug report.
(As far as I'm concerned the lack of a link is a bug.) Many of my
distributions are also mirrored at <https://bitbucket.org/tobyink>.
To submit the patch, do a pull request on GitHub or Bitbucket, or
attach a diff file to a bug report. Unless otherwise stated, I'll
assume that your contributions are licensed under the same terms as
the rest of the project.
(If using git, feel free to work in a branch. For Mercurial, I'd
prefer bookmarks within the default branch.)
view all matches for this distribution
view release on metacpan or search on metacpan
lib/Alter.pm view on Meta::CPAN
our $VERSION = '0.07';
our %EXPORT_TAGS = (
all => [ qw(
alter ego
STORABLE_freeze STORABLE_attach STORABLE_thaw
Dumper
) ],
);
our @EXPORT_OK = ( @{ $EXPORT_TAGS{'all'} } );
# for re-exportation
*STORABLE_freeze = \ &Alter::Storable::STORABLE_freeze;
*STORABLE_thaw = \ &Alter::Storable::STORABLE_thaw;
*STORABLE_attach = \ &Alter::Storable::STORABLE_attach;
*Dumper= \ &Alter::Dumper::Dumper;
eval {
die "Pure Perl requested" if $ENV{ PERL_ALTER_NO_XS}; # fake load failure
no warnings 'redefine';
lib/Alter.pm view on Meta::CPAN
Storable::freeze( $obj->Alter::image);
}
# recognized (and preferred) by Storable 2.15+, (Perl v5.8.8)
# ignored by earlier versions
sub STORABLE_attach {
my ( $class, $cloning, $ser) = @_;
++ our $attaching; # used by t/*.t, not needed for anything else
$class->Alter::reify( Storable::thaw( $ser));
}
# recognized by all versions of Storable
# incidentally, the code is equivalent to STORABLE_attach
sub STORABLE_thaw {
my ( $obj, $cloning, $ser) = @_;
++ our $thawing; # used by t/*.t, not needed for anything else
$obj->Alter::reify( Storable::thaw( $ser));
}
lib/Alter.pm view on Meta::CPAN
object, but rather create a hash as described. Re-creation of
an object is only available through C<Storable>.
For C<Storable> support the class C<Alter::Storable> is provided
with the methods C<STORABLE_freeze>, C<STORABLE_thaw> and
C<STORABLE_attach>. The three functions are also exported by C<Alter>
Their interaction with C<Storable> is described there.
Inheriting these methods allows C<Storable>'s own functions C<freeze()>
and C<thaw()> to save and restore an object's I<alter ego>s along with
the actual object body. Other C<Storable> functions, like C<store>,
lib/Alter.pm view on Meta::CPAN
Per default, both C<Alter::Dumper> and C<Alter::Storable> are made
base classes of the current class (if necessary) by C<use Alter>.
If the function C<Dumper> is imported, or if C<-dumper> is specified,
C<Alter::Dumper> is not made a base class. If any of the functions
C<STORABLE_freeze>, C<STORABLE_thaw> or C<STORABLE_attach> is imported,
or if C<-storable> is specified, C<Alter::Storable> is not made a base class.
=head3 Fallback Perl Implementation
C<Alter> is properly an XS module and a suitable C compiler is
lib/Alter.pm view on Meta::CPAN
=head2 Exports
None by default, C<alter()> and C<ego()> upon request.
Further available are C<STORABLE_freeze>, C<STORABLE_thaw> and
C<STORABLE_attach> as well as C<Dumper>. C<:all> imports all these
functions.
=head2 Environment
The environment variable C<PERL_ALTER_NO_XS> is inspected once at
view all matches for this distribution
view release on metacpan or search on metacpan
lib/Alvis/NLPPlatform.pm view on Meta::CPAN
=head2 platform_reset()
platform_reset()
The method empties or resets the structures and variables attached to
a processed document.
=head1 PLATFORM CONFIGURATION
The configuration file of the NLP Platform is composed of global
view all matches for this distribution
view release on metacpan or search on metacpan
t/test/resources/terms view on Meta::CPAN
atp-binding site ATP-binding site
atp-dependent protease ATP-dependent protease
at rich AT-rich
a+t rich region A+T-rich region
a+t-rich region A+T-rich region
attachment site attachment site
attenuated vaccine attenuated vaccine
attenuation mechanism attenuation mechanism
attenuation protein attenuation protein
attenuation region attenuation region
autolysin production autolysin production
t/test/resources/terms view on Meta::CPAN
member of this family family member
member of this genus member of this genus
membrane-anchor membrane anchor
membrane-associated protein membrane-associated protein
membrane association membrane association
membrane attachment of the protein membrane attachment of the protein
membrane dynamics membrane dynamics
membrane fraction membrane fraction
membrane fusion membrane fusion
membrane potential membrane potential
membrane protein synthesis membrane protein synthesis
t/test/resources/terms view on Meta::CPAN
periplasmic space periplasmic space
peritoneal macrophage peritoneal macrophage
permissive temperature permissive temperature
peroxide regulon peroxide regulon
peroxisome proliferators peroxisome proliferators
phage attachment site phage attachment site
phage development phage development
phage dna replication phage DNA replication
phage dna synthesis phage DNA synthesis
phage genome phage genome
phage-infected cell phage-infected cell
view all matches for this distribution
view release on metacpan or search on metacpan
If you develop a new program, and you want it to be of the greatest
possible use to the public, the best way to achieve this is to make it
free software which everyone can redistribute and change under these terms.
To do so, attach the following notices to the program. It is safest
to attach them to the start of each source file to most effectively
convey the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) <year> <name of author>
view all matches for this distribution
view release on metacpan or search on metacpan
lib/Alzabo/Driver.pm view on Meta::CPAN
connections. If you want to do this please use C<Apache::DBI> under
mod_perl or don't call C<connect()> more than once per process.
=head2 create_database
Attempts to create a new database for the schema attached to the
driver. Some drivers may accept or require more arguments than
specified above.
=head2 drop_database
Attempts to drop the database for the schema attached to the driver.
=head2 schemas
Returns a list of schemas in the specified RDBMS. This method may
accept some or all of the parameters which can be given to
view all matches for this distribution
view release on metacpan or search on metacpan
lib/Amazon/API.pm view on Meta::CPAN
target, some don't. Sparse documentation about some of the nuances of
using the REST interface directly to call AWS APIs.
We use the C<api> value as a trigger to indicate we need to set the
Action in the X-Amz-Target header. We also check to see if the
version needs to be attached to the Action value as required by some
APIs.
if ( $self->get_api ) {
if ( $self->get_version) {
$self->set_target(sprintf("%s_%s.%s", $self->get_api, $self->get_version, $self->get_action));
view all matches for this distribution
view release on metacpan or search on metacpan
If you develop a new program, and you want it to be of the greatest
possible use to humanity, the best way to achieve this is to make it
free software which everyone can redistribute and change under these
terms.
To do so, attach the following notices to the program. It is safest to
attach them to the start of each source file to most effectively convey
the exclusion of warranty; and each file should have at least the
"copyright" line and a pointer to where the full notice is found.
<one line to give the program's name and a brief idea of what it does.>
Copyright (C) 19yy <name of author>
view all matches for this distribution