view release on metacpan or search on metacpan
share/dictionary.txt view on Meta::CPAN
transom's
transoms
transparencies
transparency
transparency's
transparent
transparently
transpiration
transpiration's
transpire
transpired
transpires
view release on metacpan or search on metacpan
lib/Data/Password/zxcvbn/RankedDictionaries/French.pm view on Meta::CPAN
'transmutation' => 26753,
'transnationale' => 27583,
'transparait' => 22362,
'transparaitre' => 25989,
'transparence' => 8037,
'transparent' => 10191,
'transparente' => 13150,
'transparentes' => 20275,
'transparents' => 17947,
'transperce' => 21025,
'transpercer' => 29551,
'transpiration' => 29552,
'transplantation' => 16912,
'transport' => 860,
view release on metacpan or search on metacpan
lib/Data/Password/zxcvbn/RankedDictionaries/German.pm view on Meta::CPAN
'transformatoren' => 28740,
'transformiert' => 28741,
'transistoren' => 29702,
'transit' => 15066,
'transkription' => 23608,
'transparent' => 11249,
'transparente' => 20207,
'transparenten' => 23026,
'transparenz' => 10396,
'transport' => 2809,
'transportation' => 21077,
'transporter' => 15699,
'transportieren' => 6572,
view release on metacpan or search on metacpan
lib/Data/Password/zxcvbn/RankedDictionaries/English.pm view on Meta::CPAN
'transgression' => 13456,
'transgressions' => 17622,
'transients' => 20065,
'transitory' => 20064,
'translate' => 4325,
'transparent' => 5162,
'transpired' => 13455,
'transplant' => 2436,
'transplants' => 15819,
'transponder' => 12167,
'transsexual' => 14495,
view release on metacpan or search on metacpan
lib/Data/Pulp.pm view on Meta::CPAN
nil { ... # Do action if value is undefined }
;
$pulper->pulp( $value )
A pulper can act transparently on a single value, ARRAY, or HASH:
my $set = $pulper->prepare( $value ) # A single value list
my $set = $pulper->prepare( [ $value, ... ] )
my $set = $pulper->prepare( { key => $value, ... } ) # Throws away the keys, basically
view release on metacpan or search on metacpan
bench/contention.pl view on Meta::CPAN
# MCE::Queue (concurrent produce+consume via MCE task groups)
# ----------------------------------------------------------------
if ($has_mce) {
require MCE;
# MCE::Step runs task groups concurrently with transparent queue plumbing.
# task_end + $q->end() is the documented pattern for producer/consumer.
# MCE::Queue uses socket IPC routed through the manager process.
# True concurrent MPMC (N producers + N consumers) is not a supported
# MCE pattern — it's designed for workers→manager or pipeline flows.
# See bench/vs.pl for MCE single-process and produce→drain comparisons.
view release on metacpan or search on metacpan
lib/Data/Random/Contact/Language/EN.pm view on Meta::CPAN
transom's
transoms
transparencies
transparency
transparency's
transparent
transparently
transpiration
transpiration's
transpire
transpired
transpires
view release on metacpan or search on metacpan
lib/Data/Random/dict view on Meta::CPAN
nonterminal
nonterminals
nonterminating
nontermination
nonthermal
nontransparent
nontrivial
nonuniform
nonuniformity
nonzero
noodle
lib/Data/Random/dict view on Meta::CPAN
transmogrification
transmogrify
transpacific
transparencies
transparency
transparent
transparently
transpire
transpired
transpires
transpiring
transplant
view release on metacpan or search on metacpan
lib/Data/Rmap.pm view on Meta::CPAN
# Call the $code
if($self->want & $type) {
my $e; # local($@) and rethrow caused problems
my @got;
{
local ($@); # don't trample, cut impl. should be transparent
# call in array context. pass block for reentrancy
@got = eval { $self->call() };
$e = $@;
}
view release on metacpan or search on metacpan
t/Data/Test/Tech.pm view on Meta::CPAN
}
#########
# References to arrays and scalars in the config may
# be transparent.
#
my $current_value = $key_p->{$key};
if( ref($current_value) eq 'SCALAR') {
$current_value = $$current_value;
}
t/Data/Test/Tech.pm view on Meta::CPAN
The C<tech_config> subroutine always returns the
C<$old_value> of C<$dot_index> and only writes
the contents if C<$new_value> is defined.
The 'SCALAR' and 'ARRAY' references are transparent.
The C<tech_config> subroutine, when it senses that
the C<$dot_index> is for a 'SCALAR' and 'ARRAY' reference,
will read or write the contents instead of the reference.
The The C<tech_config> subroutine will read 'HASH" references
view release on metacpan or search on metacpan
t/Data/Test/Tech.pm view on Meta::CPAN
}
#########
# References to arrays and scalars in the config may
# be transparent.
#
my $current_value = $key_p->{$key};
if( ref($current_value) eq 'SCALAR') {
$current_value = $$current_value;
}
t/Data/Test/Tech.pm view on Meta::CPAN
The C<tech_config> subroutine always returns the
C<$old_value> of C<$dot_index> and only writes
the contents if C<$new_value> is defined.
The 'SCALAR' and 'ARRAY' references are transparent.
The C<tech_config> subroutine, when it senses that
the C<$dot_index> is for a 'SCALAR' and 'ARRAY' reference,
will read or write the contents instead of the reference.
The The C<tech_config> subroutine will read 'HASH" references
view release on metacpan or search on metacpan
lib/Data/Show.pm view on Meta::CPAN
my %style = %{ $STYLE[ $hints_ref->{'Data::Show/style'} ] };
my $termwidth = $hints_ref->{'Data::Show/termwidth'};
# Warn about side-effects of multi-arg calls to show() in scalar context...
if (defined $call_context && !$call_context && @_ > 1) {
warn "Call to show() may not be not transparent at $file line $line\n";
}
# Serialize Contextual::Return objects (can break some dumpers in the Data::Dump family)...
my @data = map { ref() =~ m{\AContextual::Return::Value}
? do {my $v = $_->Contextual::Return::DUMP(); $v =~ s[\}\n][\},\n]gxms; eval $v; }
lib/Data/Show.pm view on Meta::CPAN
You would have also received one or more of the three preceding
diagnostics. Consult their entries for suggestions on silencing
this warning.
=item C<< Call to show() may not be not transparent >>
The call to C<show()> has been inserted into a scalar context,
but was passed two or more arguments to dump. This can change
the behaviour of the surrounding code. For example, consider
the following statements:
view release on metacpan or search on metacpan
* @brief Exposes the implementation without marking functions as inline.
*/
# define XXH_PRIVATE_API
# undef XXH_PRIVATE_API
/*!
* @brief Emulate a namespace by transparently prefixing all symbols.
*
* If you want to include _and expose_ xxHash functions from within your own
* library, but also want to avoid symbol collisions with other libraries which
* may also include xxHash, you can use @ref XXH_NAMESPACE to automatically prefix
* any public symbol from xxhash library with the value of @ref XXH_NAMESPACE
view release on metacpan or search on metacpan
lib/Data/StackedHash.pm view on Meta::CPAN
=head1 DESCRIPTION
The Data::StackedHash module implements a stack of hashes; the whole
stack acts collectively and transparently as a single PERL hash, that
is, you can perform the usual operations (fetching/storing values,
I<keys>, I<delete>, etc.) on it. All the PERL buitlins which operate
on hashes are supported.
Assigning a value to a key, as in C<< $h{'a'}=1 >>, puts the key/value
view release on metacpan or search on metacpan
scripts/stag-drawtree.pl view on Meta::CPAN
my $fgcol = $im->colorAllocate(0, 0, 0);
my $linecol = $im->colorAllocate(0, 0, 0);
my $namecol = $im->colorAllocate(0, 0, 0);
my $datacol = $im->colorAllocate(255, 0, 0);
#$im->transparent($bgcol);
$im->interlaced('true');
drawbox($im, $box);
if ($out) {
view release on metacpan or search on metacpan
t/Data/Test/Tech.pm view on Meta::CPAN
}
#########
# References to arrays and scalars in the config may
# be transparent.
#
my $current_value = $key_p->{$key};
if( ref($current_value) eq 'SCALAR') {
$current_value = $$current_value;
}
t/Data/Test/Tech.pm view on Meta::CPAN
The C<tech_config> subroutine always returns the
C<$old_value> of C<$dot_index> and only writes
the contents if C<$new_value> is defined.
The 'SCALAR' and 'ARRAY' references are transparent.
The C<tech_config> subroutine, when it senses that
the C<$dot_index> is for a 'SCALAR' and 'ARRAY' reference,
will read or write the contents instead of the reference.
The The C<tech_config> subroutine will read 'HASH" references
view release on metacpan or search on metacpan
t/Data/Test/Tech.pm view on Meta::CPAN
}
#########
# References to arrays and scalars in the config may
# be transparent.
#
my $current_value = $key_p->{$key};
if( ref($current_value) eq 'SCALAR') {
$current_value = $$current_value;
}
t/Data/Test/Tech.pm view on Meta::CPAN
The C<tech_config> subroutine always returns the
C<$old_value> of C<$dot_index> and only writes
the contents if C<$new_value> is defined.
The 'SCALAR' and 'ARRAY' references are transparent.
The C<tech_config> subroutine, when it senses that
the C<$dot_index> is for a 'SCALAR' and 'ARRAY' reference,
will read or write the contents instead of the reference.
The The C<tech_config> subroutine will read 'HASH" references
view release on metacpan or search on metacpan
lib/Data/Transform.pm view on Meta::CPAN
A flag method that always returns 1. This can be used in e.g. POE to check
if the class supports L<Data::Transform::Meta>, which all Data::Transform
subclasses should, but L<POE::Filter> classes don't. Doing it this way
instead of checking if a filter is a Data::Transform subclass allows for
yet another filters implementation that is meant to transparently replace
this to be used by POE without changes to POE.
=cut
sub meta {
view release on metacpan or search on metacpan
eg/lindenmayer-gd view on Meta::CPAN
my %color = (
white => $img->colorAllocate( 255, 255, 255 ),
black => $img->colorAllocate( 0, 0, 0 ),
);
$img->transparent( $color{white} );
$img->interlaced('true');
my @statestack;
my %translate = (
view release on metacpan or search on metacpan
lib/Data/YAML.pm view on Meta::CPAN
=head1 DESCRIPTION
In the spirit of L<YAML::Tiny>, L<Data::YAML::Reader> and
L<Data::YAML::Writer> provide lightweight, dependency-free YAML
handling. While C<YAML::Tiny> is designed principally for working with
configuration files C<Data::YAML> concentrates on the transparent round-
tripping of YAML serialized Perl data structures.
As an example of why this distinction matters consider that
C<YAML::Tiny> doesn't handle hashes with keys containing non-printable
characters. This is fine for configuration files but likely to cause
view release on metacpan or search on metacpan
dw-nav will create the base of a simple Data Warehouse Navigator.
=head2 AGGREGATE NAVIGATOR
One of the main features of the Data Warehouse Navigator is the
transparent Aggregate Navigator.
The Aggregate Navigator will intercept SQL queries and generate
aggregate tables, whenever is possible.
The use of aggregate tables can speed up Data Warehouse by 100s
view release on metacpan or search on metacpan
t/extended_tests.t view on Meta::CPAN
# ---------------------------------------------------------------------------
SKIP: {
skip('Gzip::Faster not available', 3) unless $HAS_GZIP;
subtest 'EX15: gzip CSV is transparently decompressed (lines 684-691)' => sub {
plan tests => 3;
# Build a tiny CSV, gzip it, write to a temp directory
my $csv_content = "entry!number\n\"uno\"!1\n\"dos\"!2\n";
my $gzipped = Gzip::Faster::gzip($csv_content);
view release on metacpan or search on metacpan
lib/Date/Calc/Object.pod view on Meta::CPAN
=item *
Languages
Note that this module is completely transparent to the setting
of a language in "Date::Calc". This means that you can choose a
language in "Date::Calc" (with the "Language()" function) and all
dates subsequently printed by this module will automatically be
in that language - provided that you use the built-in formats of
this module, or that you pass the third parameter of the callback
view release on metacpan or search on metacpan
lib/Date/Pcalc/Object.pod view on Meta::CPAN
=item *
Languages
Note that this module is completely transparent to the setting
of a language in "Date::Pcalc". This means that you can choose a
language in "Date::Pcalc" (with the "Language()" function) and all
dates subsequently printed by this module will automatically be
in that language - provided that you use the built-in formats of
this module, or that you pass the third parameter of the callback
view release on metacpan or search on metacpan
going between and two arbitrary formats foo and bar, the function only
needs to convert foo to the base class and the base class to bar. Ie:
Gregorian <--> Base class <--> Hebrew
The base class includes a B<Convert> method to do this transparently.
Nothing is exported because it wouldn't make any sense to export. :)
=head1 DESCRIPTION
view release on metacpan or search on metacpan
(addition and subtraction), and provides many convenient methods
for retrieving portions of a date/time.
This module properly supports the Olson time zone database, meaning
that historical time zone information, and more importantly, daylight
saving time rules, can be handled transparently, simply by setting the
correct time zone. This is done by using the DateTime::TimeZone
module.
INSTALLATION
view release on metacpan or search on metacpan
lib/DateTime/Lite.pm view on Meta::CPAN
# And more complex forms too
my $dt = DateTime::Lite->now( locale => 'he-IL-u-ca-hebrew-tz-jeruslm' );
my $dt = DateTime::Lite->now( locale => 'ja-Kana-t-it' );
my $dt = DateTime::Lite->now( locale => 'ar-SA-u-nu-latn' );
Locale data is resolved dynamically by L<DateTime::Locale::FromCLDR> via L<Locale::Unicode::Data>, so tags like C<he-IL-u-ca-hebrew-tz-jeruslm> or C<ja-Kana-t-it> work transparently without any additional installed modules.
Additionally, if the locale tag carries a L<Unicode timezone extension|Locale::Unicode/"Unicode extensions"> (C<-u-tz->), and no explicit C<time_zone> argument is provided to the constructor, C<DateTime::Lite> will automatically resolve the correspon...
# time_zone is inferred as 'Asia/Jerusalem' from the -u-tz-jeruslm extension
my $dt = DateTime::Lite->now( locale => 'he-IL-u-ca-hebrew-tz-jeruslm' );
view release on metacpan or search on metacpan
examples/web/reset.css view on Meta::CPAN
padding: 0;
border: 0;
outline: 0;
font-size: 100%;
vertical-align: baseline;
background: transparent;
}
body {
line-height: 1;
}
ol, ul {
view release on metacpan or search on metacpan
Docs/Debug-Fork-Tmux-Config.html view on Meta::CPAN
margin: 0;
padding: 1ex;
}
A:link, A:visited {
background: transparent;
color: #006699;
}
A[href="#POD_ERRORS"] {
background: transparent;
color: #FF0000;
}
DIV {
border-width: 0;
Docs/Debug-Fork-Tmux-Config.html view on Meta::CPAN
padding: 1em;
white-space: pre;
}
.pod H1 {
background: transparent;
color: #006699;
font-size: large;
}
.pod H1 A { text-decoration: none; }
.pod H2 A { text-decoration: none; }
.pod H3 A { text-decoration: none; }
.pod H4 A { text-decoration: none; }
.pod H2 {
background: transparent;
color: #006699;
font-size: medium;
}
.pod H3 {
background: transparent;
color: #006699;
font-size: medium;
font-style: italic;
}
.pod H4 {
background: transparent;
color: #006699;
font-size: medium;
font-weight: normal;
}
view release on metacpan or search on metacpan
2.10 Fri Jan 15 16:14:02 CET 2010
- fix blending factors to avoid white-out when fow_intensity > 0.
2.09 Tue Dec 22 01:40:24 CET 2009
- implement smooth fow/lighting transitions by blending.
- make fow texture configurable and add stipple/transparent versions.
- empty "Host" field will now default to gameserver.deliantra.net.
- do not crash when the user enters an invalid value into "Host".
- fix positional rounding on (pre-c99) windows.
- use a pack/unpack alignment of 1 by default everywhere, drop alignment
code in fow_texture.