view release on metacpan or search on metacpan
maxminddb/src/maxminddb-compat-util.h view on Meta::CPAN
* FreeBSD source, along with the relevant copyright notice.
*
* It'd be nicer to simply use the functions available on the system if they
* exist, but there doesn't seem to be a good way to detect them without also
* defining things like _GNU_SOURCE, which we want to avoid, because then we
* end up _accidentally_ using GNU features without noticing, which then
* breaks on systems like OSX.
*
* C is fun! */
/* Applies to memmem implementation */
view all matches for this distribution
view release on metacpan or search on metacpan
libsecp256k1/build/CMakeFiles/3.21.4/CompilerIdC/CMakeCCompilerId.c view on Meta::CPAN
#endif
#if defined(__GNUC__)
# define SIMULATE_ID "GNU"
#endif
/* __INTEL_LLVM_COMPILER = VVVVRP prior to 2021.2.0, VVVVRRPP for 2021.2.0 and
* later. Look for 6 digit vs. 8 digit version number to decide encoding.
* VVVV is no smaller than the current year when a version is released.
*/
#if __INTEL_LLVM_COMPILER < 1000000L
# define COMPILER_VERSION_MAJOR DEC(__INTEL_LLVM_COMPILER/100)
# define COMPILER_VERSION_MINOR DEC(__INTEL_LLVM_COMPILER/10 % 10)
view all matches for this distribution
view release on metacpan or search on metacpan
Licenses are intended to guarantee your freedom to share and change
free software--to make sure the software is free for all its users.
This license, the Lesser General Public License, applies to some
specially designated software packages--typically libraries--of the
Free Software Foundation and other authors who decide to use it. You
can use it too, but we suggest you first think carefully about whether
this license or the ordinary General Public License is the better
strategy to use in any particular case, based on the explanations below.
When we speak of free software, we are referring to freedom of use,
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system which is
implemented by public license practices. Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.
This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.
view all matches for this distribution
view release on metacpan or search on metacpan
Licenses are intended to guarantee your freedom to share and change
free software--to make sure the software is free for all its users.
This license, the Lesser General Public License, applies to some
specially designated software packages--typically libraries--of the
Free Software Foundation and other authors who decide to use it. You
can use it too, but we suggest you first think carefully about whether
this license or the ordinary General Public License is the better
strategy to use in any particular case, based on the explanations below.
When we speak of free software, we are referring to freedom of use,
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system which is
implemented by public license practices. Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.
This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.
view all matches for this distribution
view release on metacpan or search on metacpan
published by the Free Software Foundation. If the Library as you
received it does not specify a version number of the GNU Lesser
General Public License, you may choose any version of the GNU Lesser
General Public License ever published by the Free Software Foundation.
If the Library as you received it specifies that a proxy can decide
whether future versions of the GNU Lesser General Public License shall
apply, that proxy's public statement of acceptance of any version is
permanent authorization for you to choose that version for the
Library.
view all matches for this distribution
view release on metacpan or search on metacpan
published by the Free Software Foundation. If the Library as you
received it does not specify a version number of the GNU Lesser
General Public License, you may choose any version of the GNU Lesser
General Public License ever published by the Free Software Foundation.
If the Library as you received it specifies that a proxy can decide
whether future versions of the GNU Lesser General Public License shall
apply, that proxy's public statement of acceptance of any version is
permanent authorization for you to choose that version for the
Library.
view all matches for this distribution
view release on metacpan or search on metacpan
published by the Free Software Foundation. If the Library as you
received it does not specify a version number of the GNU Lesser
General Public License, you may choose any version of the GNU Lesser
General Public License ever published by the Free Software Foundation.
If the Library as you received it specifies that a proxy can decide
whether future versions of the GNU Lesser General Public License shall
apply, that proxy's public statement of acceptance of any version is
permanent authorization for you to choose that version for the
Library.
view all matches for this distribution
view release on metacpan or search on metacpan
libuv/CONTRIBUTING.md view on Meta::CPAN
$ git clone https://github.com/username/libuv.git
$ cd libuv
$ git remote add upstream https://github.com/libuv/libuv.git
```
Now decide if you want your feature or bug fix to go into the master branch
or the stable branch. As a rule of thumb, bug fixes go into the stable branch
while new features go into the master branch.
The stable branch is effectively frozen; patches that change the libuv
API/ABI or affect the run-time behavior of applications get rejected.
libuv/CONTRIBUTING.md view on Meta::CPAN
does not align with that of a project maintainers.
### BRANCH
Okay, so you have decided on the proper branch. Create a feature branch
and start hacking:
```
$ git checkout -b my-feature-branch -t origin/v1.x
```
view all matches for this distribution
view release on metacpan or search on metacpan
inc/inc_IPC-Cmd/IPC/Cmd.pm view on Meta::CPAN
or if your system is able to work with C<IPC::Open3> -- See below).
This element will be C<undef> if this is not the case.
=back
See the C<HOW IT WORKS> Section below to see how C<IPC::Cmd> decides
what modules or function calls to use when issuing a command.
=cut
sub run {
view all matches for this distribution
view release on metacpan or search on metacpan
property right claims or to contest validity of any such claims; this section has
the sole purpose of protecting the integrity of the free software distribution
system, which is implemented by public license practices. Many people have
made generous contributions to the wide range of software distributed through
that system in reliance on consistent application of that system; it is up to the
author/donor to decide if he or she is willing to distribute software through any
other system and a licensee cannot impose that choice.
This section is intended to make thoroughly clear what is believed to be a
consequence of the rest of this License.
view all matches for this distribution
view release on metacpan or search on metacpan
lib/AlignDB/Codon.pm view on Meta::CPAN
'', '',
'Echinoderm and Flatworm Mitochondrial', # 9
'Euplotid Nuclear', # 10
'Bacterial, Archaeal and Plant Plastid', # 11
'Alternative Yeast Nuclear', # 12
'Ascidian Mitochondrial', # 13
'Alternative Flatworm Mitochondrial', # 14
'Blepharisma Nuclear', # 15
'Chlorophycean Mitochondrial', # 16
'', '', '', '',
'Trematode Mitochondrial', # 21
lib/AlignDB/Codon.pm view on Meta::CPAN
my %one2three = (
A => 'Ala', # Alanine
R => 'Arg', # Arginine
N => 'Asn', # Asparagine
D => 'Asp', # Aspartic acid
C => 'Cys', # Cysteine
Q => 'Gln', # Glutamine
E => 'Glu', # Glutamic acid
G => 'Gly', # Glycine
H => 'His', # Histidine
I => 'Ile', # Isoleucine
L => 'Leu', # Leucine
K => 'Lys', # Lysine
lib/AlignDB/Codon.pm view on Meta::CPAN
S => 'Ser', # Serine
T => 'Thr', # Threonine
W => 'Trp', # Tryptophan
Y => 'Tyr', # Tyrosine
V => 'Val', # Valine
B => 'Asx', # Aspartic acid or Asparagine
Z => 'Glx', # Glutamine or Glutamic acid
X => 'Xaa', # Any or unknown amino acid
'*' => '***', # Stop codon
);
my %three2one = reverse(%one2three);
$self->{one2three} = \%one2three;
lib/AlignDB/Codon.pm view on Meta::CPAN
my $aa_code = substr( $peptide, $pos, 1 );
if ( $three_of->{$aa_code} ) {
$converted .= $three_of->{$aa_code};
}
else {
Carp::confess "Wrong single-letter amino acid code [$aa_code]!\n";
$converted .= ' ' x 3;
}
}
return $converted;
}
lib/AlignDB/Codon.pm view on Meta::CPAN
$aa_code = ucfirst $aa_code;
if ( $one_of->{$aa_code} ) {
$converted .= $one_of->{$aa_code};
}
else {
warn "Wrong three-letter amino acid code [$aa_code]!\n";
$converted .= ' ' x 3;
}
}
view all matches for this distribution
view release on metacpan or search on metacpan
lib/Aliyun.pm view on Meta::CPAN
$method->set_sms_param('{"rain":"ä¸é¨","temper":"18"}');
my $method2 = Aliyun::Method::FcIotQrycard->new();
$method2->set_bill_source('ICCID');
$method2->set_bill_real('123123');
$method2->set_iccid('123123');
my $request = Aliyun::Request->new();
$request->get($auth, $method, sub {
say Dumper $_[0];
});
view all matches for this distribution
view release on metacpan or search on metacpan
inc/Module/Install.pm view on Meta::CPAN
use File::Path ();
use vars qw{$VERSION $MAIN};
BEGIN {
# All Module::Install core packages now require synchronised versions.
# This will be used to ensure we don't accidentally load old or
# different versions of modules.
# This is not enforced yet, but will be some time in the next few
# releases once we can make sure it won't clash with custom
# Module::Install extensions.
$VERSION = '1.06';
view all matches for this distribution
view release on metacpan or search on metacpan
inc/Module/Install.pm view on Meta::CPAN
use File::Path ();
use vars qw{$VERSION $MAIN};
BEGIN {
# All Module::Install core packages now require synchronised versions.
# This will be used to ensure we don't accidentally load old or
# different versions of modules.
# This is not enforced yet, but will be some time in the next few
# releases once we can make sure it won't clash with custom
# Module::Install extensions.
$VERSION = '1.14';
view all matches for this distribution
view release on metacpan or search on metacpan
lib/CWB/CEQL/Parser.pm view on Meta::CPAN
Each B<DPP rule> is implemented as a B<Perl subroutine> (or, more precisely,
B<method>). It is invoked by the parser with an input string that is expected
to be a constituent of the respective type, and returns its analysis of this
constituent. In the typical application of DPP grammars, the return value is
a string representing (part of) a low-level query expression, but grammar
authors may also decide to return arbitrary data structures. In the B<rule
body>, other grammar rules can be applied to the full input string, a
substring, or an arbitrarily transformed substring using the B<Call> method.
It is also possible to invoke the shift-reduce-type parser with the B<Apply>
method. Both methods return an analysis of the given substring, which can
then be integrated with the analyses of other substrings and the parsing
lib/CWB/CEQL/Parser.pm view on Meta::CPAN
=over 4
=item 1.
examine the input string to decide whether it appears to be a suitable
constituent, and to determine its internal structure
=item 2.
if the test in Step 1 fails, B<die> with a meaningful error message;
lib/CWB/CEQL/Parser.pm view on Meta::CPAN
The simplest DPP rules are stand-alone rules that transform their input string
directly without invoking any subrules. These rules typically make use of regular
expression substitutions and correspond to one part of the substitution cascade
in a traditional implementation of simple query languages. In contrast to such
cascades, DPP rules apply only to relevant parts of the input string and cannot
accidentally modify other parts of the simple query. The example below transforms
a search term with shell-style wildcards (C<?> and C<*>) into a regular expression.
Note how the input string is first checked to make sure it does not contain any
other metacharacters that might have a special meaning in the generated regular
expression, and B<die>s with an informative error message otherwise.
view all matches for this distribution
view release on metacpan or search on metacpan
# else
# define D_PPP_TO_FOLD_CALLEE(s,r,l) to_utf8_fold(s,r,l)
# endif
# else /* Below is 5.15.6, which failed to make the macros available
# outside of core, so we have to use the 'Perl_' form. khw
# decided it was easier to just handle this case than have to
# document the exception, and make an exception in the tests below
# */
# define D_PPP_TO_LOWER_CALLEE(s,r,l) \
Perl__to_utf8_lower_flags(aTHX_ s, r, l, 0, NULL)
# define D_PPP_TO_TITLE_CALLEE(s,r,l) \
view all matches for this distribution
view release on metacpan or search on metacpan
- The test suites do almost no failure testing. Use Devel::Cover to see all
the failure cases that aren't covered.
- Look into allowing other SHA hashes for PSS and OAEP.
- Decide if RIPEMD160 should be non-optional. Module version 0.05 looks like
it has an excellent test pass rate.
- t/16-serialize.t is just verifying we don't die horribly. We should verify
that it's actually working.
view all matches for this distribution
view release on metacpan or search on metacpan
lib/Date/Extract.pm view on Meta::CPAN
This controls both the input time zone and output time zone.
=item prefers
This argument decides what happens when an ambiguous date appears in the
input. For example, "Friday" may refer to any number of Fridays. The valid
options for this argument are:
=over 4
view all matches for this distribution
view release on metacpan or search on metacpan
software is free for all its users.
This license, the Lesser General Public License, applies to
some specially designated software packages--typically
libraries--of the Free Software Foundation and other authors
who decide to use it. You can use it too, but we suggest you
first think carefully about whether this license or the ordinary
General Public License is the better strategy to use in any
particular case, based on the explanations below.
When we speak of free software, we are referring to freedom
of protecting the integrity of the free software distribution
system which is implemented by public license practices.
Many people have made generous contributions to the wide
range of software distributed through that system in reliance
on consistent application of that system; it is up to the
author/donor to decide if he or she is willing to distribute
software through any other system and a licensee cannot
impose that choice.
This section is intended to make thoroughly clear what is
believed to be a consequence of the rest of this License.
view all matches for this distribution
view release on metacpan or search on metacpan
NAME
Alt::Sex::INGY - INGY's Alternate version of Sex
DESCRIPTION
After having Sex under Schwern's governance for 12 years, I decided it
was time for an Alternative.
This version of Sex supports the participation of multiple random
entities.
view all matches for this distribution
view release on metacpan or search on metacpan
t/Test/Builder.pm view on Meta::CPAN
=cut
sub ok {
my($self, $test, $name) = @_;
# $test might contain an object which we don't want to accidentally
# store, so we turn it into a boolean.
$test = $test ? 1 : 0;
unless( $self->{Have_Plan} ) {
require Carp;
view all matches for this distribution
view release on metacpan or search on metacpan
lib/Tickit/Widget.pm view on Meta::CPAN
the C<get_style_*> methods may return different results. No resizing or
redrawing is necessarily performed; but the widget can use
C<style_reshape_keys>, C<style_reshape_textwidth_keys> or C<style_redraw_keys>
to declare which style keys should cause automatic reshaping or redrawing. In
addition it can override the C<on_style_changed_values> method to inspect the
changes and decide for itself.
=cut
# This is cached, so will need invalidating on style loads
my %KEYS_BY_TYPE_CLASS_TAG;
view all matches for this distribution
view release on metacpan or search on metacpan
avs_count_getword
avs_countnext
avs_default_options
avs_define_valtype
avs_define_valtype_multiple
avs_deletedocid
avs_enddoc
avs_errmsg
avs_getindexmode
avs_getindexversion
avs_getindexversion_counts_v
avs_search_ex
avs_search_genrank
avs_search_getdata
avs_search_getdatalen
avs_search_getdate
avs_search_getdocid
avs_search_getdocidlen
avs_search_getrelevance
avs_setdocdata
avs_setdocdate
avs_setdocdatetime
avs_setparseflags
avs_define_valtype(name, minval, maxval, valtype_p)
avs_define_valtype_multiple(name, minval, maxval, numvalues, valtype_p)
avs_deletedocid(idx, pDocId, pCount)
avs_enddoc(idx)
avs_errmsg(code)
avs_search_getdatalen(searchHdl)
avs_search_getdate(psearchHdl, year, month, day)
avs_search_getdocid(searchHdl)
avs_search_getdocidlen(searchHdl)
avs_search_getrelevance(psearchHdl)
avs_setdocdata(idx, pDocData, len)
=item I<avs_newdoc> UNIMPLEMENTED
=item I<avs_search_getdata_copy> UNIMPLEMENTED
=item I<avs_search_getdocid_copy> UNIMPLEMENTED
=item I<avs_search_getrelevance> RETURN ARGUMENT
=back
view all matches for this distribution
view release on metacpan or search on metacpan
lib/Alter.pm view on Meta::CPAN
++ 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
that both (all) destructors are called as needed. Perl only calls the
first one it meets on the C<@ISA> tree and that's it.
Otherwise the fallback implementation works like the original. If
compilation has problems, it should allow you to run test cases to
help decide if it's worth trying. To make sure that production code
doesn't inadvertently run with the Perl implementation
Alter::is_xs or die "XS implementation of Alter required";
can be used.
lib/Alter.pm view on Meta::CPAN
functions.
=head2 Environment
The environment variable C<PERL_ALTER_NO_XS> is inspected once at
load time to decide whether to load the XS version of C<Alter> or
the pure Perl fallback. At run time it has no effect.
=head2 Description
The C<Alter> module is meant to facilitate the creation of classes
view all matches for this distribution
view release on metacpan or search on metacpan
bin/linkMpca view on Meta::CPAN
open(INH,"<$stem.dochash");
my $buf = "";
read(INF,$buf,4);
my $I = unpack("i",$buf);
my $dhash = "";
my $docid = 0;
# the binary read and unpack() combo reads
# entries from an MPCA Vec_t file
my %hashrank = ();
for (my $i=0; $i<$I; $i++) {
read(INF,$buf,4);
view all matches for this distribution
view release on metacpan or search on metacpan
t/test-data/to-split/29.xml view on Meta::CPAN
<urls>
<url>http://searchenginewatch.com/searchday/article.php/3592876</url>
</urls>
</acquisitionData>
<canonicalDocument>
<section>At long last, Google has launched its ownGoogle Finance service. For years, those seeking specialty financial information via Google have been sent to competitors such as Yahoo and MSN. Now Google's providing financial information di...
<metaData>
<meta name="title">Google Launches Google Finance</meta>
<meta name="dc:type">text/html</meta>
</metaData>
<links>
t/test-data/to-split/29.xml view on Meta::CPAN
<urls>
<url>http://blog.outer-court.com/archive/2006-05-30-n12.html</url>
</urls>
</acquisitionData>
<canonicalDocument>
<section>Some bloggers are complaining that Google didnât have a Memorial day logo yesterday. Memorial Day âcommemorates U.S. men and women who have died in military service,âWikipedia explains. From a comment at Newsbusters by Warner T...
<metaData>
<meta name="title">Complaints Due to Lack of Google Memorial Day Logo</meta>
<meta name="dc:date">Thu, 01 Jun 2006 02:44:56 GMT</meta>
<meta name="dc:type">text/html</meta>
</metaData>
t/test-data/to-split/29.xml view on Meta::CPAN
<urls>
<url>http://searchenginewatch.com/searchday/article.php/3612406</url>
</urls>
</acquisitionData>
<canonicalDocument>
<section>Links to the week's topics from search engine forums across the web. What Top 5 Skills Would You Study to Become a Better SEO? Search Engine Watch Forums "What skills would you put on your Matrix 'must have' list for your career path...
<metaData>
<meta name="title">Search Engine Forums Spotlight</meta>
<meta name="dc:type">text/html</meta>
</metaData>
<links>
view all matches for this distribution
view release on metacpan or search on metacpan
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system, which is
implemented by public license practices. Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.
This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.
view all matches for this distribution
view release on metacpan or search on metacpan
lib/Alvis/Logger.pm view on Meta::CPAN
# $Id: Logger.pm,v 1.1 2005/06/17 15:45:56 mike Exp $
# This is a simple logging object that I have accidentally implemented
# several different 90% subsets of in half a dozen different projects.
# It's time to get it done once, properly.
package Alvis::Logger;
use strict;
view all matches for this distribution