view release on metacpan or search on metacpan
lib/Acme/Web20/Validator/Rule/UseCSS.pm view on Meta::CPAN
__PACKAGE__->name('Using Cascading Style Sheet?');
sub validate {
my ($self, $res) = @_;
$self->is_ok($res->content =~ m!<link.*?rel="stylesheet".*?>!);
}
1;
view release on metacpan or search on metacpan
CONTRIBUTING view on Meta::CPAN
For translations of error messages and other strings embedded in the
code, check with me first. Sometimes the English strings may not in
a stable state, so it would be a waste of time translating them.
Coding Style
I tend to write using something approximating the Allman style, using
tabs for indentation and Unix-style line breaks.
* <http://en.wikipedia.org/wiki/Indent_style#Allman_style>
* <http://www.derkarl.org/why_to_tabs.html>
I nominally encode all source files as UTF-8, though in practice most of
them use a 7-bit-safe ASCII-compatible subset of UTF-8.
view release on metacpan or search on metacpan
ex/mod/t/pod-coverage.t view on Meta::CPAN
eval "use Test::Pod::Coverage $min_tpc";
plan skip_all => "Test::Pod::Coverage $min_tpc required for testing POD coverage"
if $@;
# Test::Pod::Coverage doesn't require a minimum Pod::Coverage version,
# but older versions don't recognize some common documentation styles
my $min_pc = 0.18;
eval "use Pod::Coverage $min_pc";
plan skip_all => "Pod::Coverage $min_pc required for testing POD coverage"
if $@;
view release on metacpan or search on metacpan
lib/Acme/YAPC/Okinawa/ppport.h view on Meta::CPAN
of F<lib/Acme/YAPC/Okinawa/ppport.h> if you intend to be backward compatible only
down to a certain Perl version.
=head2 --cplusplus
Usually, F<lib/Acme/YAPC/Okinawa/ppport.h> will detect C++ style comments and
replace them with C style comments for portability reasons.
Using this option instructs F<lib/Acme/YAPC/Okinawa/ppport.h> to leave C++
comments untouched.
=head2 --quiet
lib/Acme/YAPC/Okinawa/ppport.h view on Meta::CPAN
}
}
if ($cppc) {
my $s = $cppc != 1 ? 's' : '';
warning("Uses $cppc C++ style comment$s, which is not portable");
}
my $s = $warnings != 1 ? 's' : '';
my $warn = $warnings ? " ($warnings warning$s)" : '';
info("Analysis completed$warn");
view release on metacpan or search on metacpan
lib/Acme/constant.pm view on Meta::CPAN
This pragma lets you make inconstant constants, just like the constants
the users of Ruby or Opera (before Opera 14, that is) already enjoyed.
Unlike Perl constants, that are replaced at compile time, Acme
constants, in true dynamic programming language style, can be modified
even after declaration.
Just like constants generated with standard C<use constant> pragma, the
constants declared with C<use Acme::Constant> don't have any sigils.
This makes using constants easier, as you don't have to remember what
view release on metacpan or search on metacpan
t/pod-coverage.t view on Meta::CPAN
eval "use Test::Pod::Coverage $min_tpc";
plan skip_all => "Test::Pod::Coverage $min_tpc required for testing POD coverage"
if $@;
# Test::Pod::Coverage doesn't require a minimum Pod::Coverage version,
# but older versions don't recognize some common documentation styles
my $min_pc = 0.18;
eval "use Pod::Coverage $min_pc";
plan skip_all => "Pod::Coverage $min_pc required for testing POD coverage"
if $@;
view release on metacpan or search on metacpan
t/pod-coverage.t view on Meta::CPAN
eval "use Test::Pod::Coverage $min_tpc";
plan skip_all => "Test::Pod::Coverage $min_tpc required for testing POD coverage"
if $@;
# Test::Pod::Coverage doesn't require a minimum Pod::Coverage version,
# but older versions don't recognize some common documentation styles
my $min_pc = 0.18;
eval "use Pod::Coverage $min_pc";
plan skip_all => "Pod::Coverage $min_pc required for testing POD coverage"
if $@;
view release on metacpan or search on metacpan
t/pod-coverage.t view on Meta::CPAN
eval "use Test::Pod::Coverage $min_tpc";
plan skip_all => "Test::Pod::Coverage $min_tpc required for testing POD coverage"
if $@;
# Test::Pod::Coverage doesn't require a minimum Pod::Coverage version,
# but older versions don't recognize some common documentation styles
my $min_pc = 0.18;
eval "use Pod::Coverage $min_pc";
plan skip_all => "Pod::Coverage $min_pc required for testing POD coverage"
if $@;
view release on metacpan or search on metacpan
t/pod-coverage.t view on Meta::CPAN
eval "use Test::Pod::Coverage $min_tpc";
plan skip_all => "Test::Pod::Coverage $min_tpc required for testing POD coverage"
if $@;
# Test::Pod::Coverage doesn't require a minimum Pod::Coverage version,
# but older versions don't recognize some common documentation styles
my $min_pc = 0.18;
eval "use Pod::Coverage $min_pc";
plan skip_all => "Pod::Coverage $min_pc required for testing POD coverage"
if $@;
view release on metacpan or search on metacpan
CONTRIBUTING.mkdn view on Meta::CPAN
$ prove -lv t/some_test_file.t
For most of my distributions, `prove` is entirely sufficient for you to test any
patches you have. I use `prove` for 99% of my testing during development.
### Code style and tidying
Please try to match any existing coding style. If there is a `.perltidyrc`
file, please install Perl::Tidy and use perltidy before submitting patches.
If there is a `tidyall.ini` file, you can also install Code::TidyAll and run
`tidyall` on a file or `tidyall -a` to tidy all files.
view release on metacpan or search on metacpan
t/pod-coverage.t view on Meta::CPAN
eval "use Test::Pod::Coverage $min_tpc";
plan skip_all => "Test::Pod::Coverage $min_tpc required for testing POD coverage"
if $@;
# Test::Pod::Coverage doesn't require a minimum Pod::Coverage version,
# but older versions don't recognize some common documentation styles
my $min_pc = 0.18;
eval "use Pod::Coverage $min_pc";
plan skip_all => "Pod::Coverage $min_pc required for testing POD coverage"
if $@;
view release on metacpan or search on metacpan
lib/Acrux/DBI/Dump.pm view on Meta::CPAN
$delimiter = $1;
} elsif ($s =~ /^(\s+)/s or $s =~ /^(\w+)/) { # whitespaces or general name
$chunk = $1;
} elsif ($s =~ /^--.*(?:\n|\z)/p # double-dash comment
or $s =~ /^\#.*(?:\n|\z)/p # hash comment
or $s =~ /^\/\*(?:[^\*]|\*[^\/])*(?:\*\/|\*\z|\z)/p # C-style comment
or $s =~ /^'(?:[^'\\]*|\\(?:.|\n)|'')*(?:'|\z)/p # single-quoted literal text
or $s =~ /^"(?:[^"\\]*|\\(?:.|\n)|"")*(?:"|\z)/p # double-quoted literal text
or $s =~ /^`(?:[^`]*|``)*(?:`|\z)/p ) { # schema-quoted literal text
$chunk = ${^MATCH};
} else {
view release on metacpan or search on metacpan
t/00-pod-coverage.t view on Meta::CPAN
my $ver = 1.08;
eval "use Test::Pod::Coverage $ver";
plan skip_all => "Test::Pod::Coverage $ver required for testing POD coverage" if $@;
# Test::Pod::Coverage doesn't require a minimum Pod::Coverage version,
# but older versions don't recognize some common documentation styles
my $verpc = 0.18;
eval "use Pod::Coverage $verpc";
plan skip_all => "Pod::Coverage $verpc required for testing POD coverage" if $@;
plan skip_all => "Currently a developer-only test" unless -d '.svn' || -d ".git";
view release on metacpan or search on metacpan
lib/Activator/Emailer.pm view on Meta::CPAN
the TT chomping close tag (C<-%]>) to maintain format.
=head2 File 1: html_header
This is the most basic header, but you can add as much HTML as you
like, including limited style and script tags:
<html>
<body>
=head2 File 2: html_body
view release on metacpan or search on metacpan
t/03-pod-coverage.t view on Meta::CPAN
eval "use Test::Pod::Coverage $min_tpc";
plan skip_all => "Test::Pod::Coverage $min_tpc required for testing POD coverage"
if $@;
# Test::Pod::Coverage doesn't require a minimum Pod::Coverage version,
# but older versions don't recognize some common documentation styles
my $min_pc = 0.18;
eval "use Pod::Coverage $min_pc";
plan skip_all => "Pod::Coverage $min_pc required for testing POD coverage"
if $@;
view release on metacpan or search on metacpan
t/pod-coverage.t view on Meta::CPAN
eval "use Test::Pod::Coverage $min_tpc";
plan skip_all => "Test::Pod::Coverage $min_tpc required for testing POD coverage"
if $@;
# Test::Pod::Coverage doesn't require a minimum Pod::Coverage version,
# but older versions don't recognize some common documentation styles
my $min_pc = 0.18;
eval "use Pod::Coverage $min_pc";
plan skip_all => "Pod::Coverage $min_pc required for testing POD coverage"
if $@;
view release on metacpan or search on metacpan
lib/AddressBook/DB/BBDB.pm view on Meta::CPAN
["Henry" The first name - a string
"Laxen" The last name - a string
("Henry, Enrique") Also Known As - comma separated list
"Elegant Solution" Business name - a string
(["home" 415 789 1159 0] Phone number field - US style
["fax" 415 789 1156 0] Phone number field - US style
["mazatlan" "011-5269-164195"] Phone number field - International style
)
(["mailing" "PMB 141" Address field - There are 3 fields for
"524 San Anselmo Ave." "" for the street address, then one each
"San Anselmo" "CA" (94960 2614)" for City, State, and Zip Code
]
view release on metacpan or search on metacpan
lib/Ado/Plugin/AdoHelpers.pm view on Meta::CPAN
}
# render
my $css = '';
#everything in separate stylesheet begin end block or <link>
foreach my $a (@$assets_list) {
if ($a =~ $file_re) { # a file
$css .= qq|<link href="$a" rel='stylesheet' type='text/css' />\n|;
}
elsif (ref $a eq 'CODE') { # a code
$css .= $c->stylesheet($a) . $/;
}
else { # a string
$css .= $c->stylesheet(sub {$a}) . $/;
}
}
return $css;
}
lib/Ado/Plugin/AdoHelpers.pm view on Meta::CPAN
jQuery( function($){ $('#ado-img').popup() });
% end;
# render in templates/partials/head.html.ep
%== head_css;
<link href="css/ado.css" rel='stylesheet' type='text/css' />
<link href='//fonts.googleapis.com/css?family=Ubuntu&subset=latin,cyrillic'
rel='stylesheet' type='text/css' />
%== head_javascript;
=head2 to_json
Suitable for preparing JavaScript
view release on metacpan or search on metacpan
t/pod-coverage.t view on Meta::CPAN
eval "use Test::Pod::Coverage $min_tpc";
plan skip_all => "Test::Pod::Coverage $min_tpc required for testing POD coverage"
if $@;
# Test::Pod::Coverage doesn't require a minimum Pod::Coverage version,
# but older versions don't recognize some common documentation styles
my $min_pc = 0.18;
eval "use Pod::Coverage $min_pc";
plan skip_all => "Pod::Coverage $min_pc required for testing POD coverage"
if $@;
view release on metacpan or search on metacpan
dyncall/configure.bat view on Meta::CPAN
) ELSE (
buildsys\scripts\conf-nds.bat
)
)
REM Generate *nix style make files? @@@ maybe we should just always do that
IF [%CONFIG_MAKE%]==[make] (
FOR /F "USEBACKQ TOKENS=*" %%X IN (`CD`) DO (
FOR /R %%F IN (Makefile.generic) DO IF EXIST %%F (
ECHO VPATH = %%~dF%%~pF.>%%~pF%%~nF
ECHO include %%X\Makefile.config>>%%~pF%%~nF
view release on metacpan or search on metacpan
lib/Agent/TCLI/Package/Net/HTTP.pm view on Meta::CPAN
first request. The default is 1.
type: Param
---
Agent::TCLI::Command:
name: http
call_style: session
command: tcli_http
contexts:
ROOT: http
handler: establish_context
help: http web cient environment
lib/Agent/TCLI/Package/Net/HTTP.pm view on Meta::CPAN
topic: net
usage: http tget url=http:\example.com\request resp=404
---
Agent::TCLI::Command:
name: tget
call_style: session
command: tcli_http
contexts:
http: tget
handler: get
help: makes a requests and expects a specific response code
lib/Agent/TCLI/Package/Net/HTTP.pm view on Meta::CPAN
url:
topic: net
usage: tget tget url=http:\example.com\request resp=404
---
Agent::TCLI::Command:
call_style: session
command: tcli_http
contexts:
http: cget
handler: get
help: makes a requests and returns response code
view release on metacpan or search on metacpan
lib/Agent/TCLI/Command.pm view on Meta::CPAN
'name' => 'cmd1',
'contexts' => {'/' => 'cmd1'},
'help' => 'cmd1 help',
'usage' => 'cmd1 usage',
'topic' => 'test',
'call_style'=> 'session',
'command' => 'test1',
'handler' => 'cmd1',
'parameters' => {
'test_verbose' => $test_verbose
'paramint' => $paramint,
lib/Agent/TCLI/Command.pm view on Meta::CPAN
contexts:
'/' : cmd1
help: cmd1 help
usage: cmd1 usage
topic: test
call_style: session
command: test1
handler: cmd1
parameters:
test_verbose: verbose
paramint: paramint
lib/Agent/TCLI/Command.pm view on Meta::CPAN
POE event driven command
=cut
my @handler :Field :All('handler');
=item call_style
This is a holdover to facilitate migration from the older style method
of calling commands with an oob, to the new POE parameter use. The value
'poe' means the command is called directly with the normal POE KERNEL
HEAP and ARGs. 'session' means that a POE event handler is called.
B<call_style> will only accept SCALAR type values.
=cut
my @call_style :Field :All('call_style');
=item contexts
A hash of the contexts that the command may be called from. This needs to
be written up much better in a separate section, as it is very complicated.
lib/Agent/TCLI/Command.pm view on Meta::CPAN
## usage => { type => Params::Validate::SCALAR }, #required
## topic => { optional => 1, type => Params::Validate::SCALAR },
## name => { type => Params::Validate::SCALAR }, #required
## command => { type => ( Params::Validate::SCALAR | Params::Validate::CODEREF ) }, #required
## context => { optional => 1, type => Params::Validate::ARRAYREF },
## style => { optional => 1, type => Params::Validate::SCALAR },
## start => { optional => 1, type => Params::Validate::CODEREF },
## handler => { optional => 1, type => Params::Validate::SCALAR },
## stop => { optional => 1, type => Params::Validate::CODEREF },
## } );
#
lib/Agent/TCLI/Command.pm view on Meta::CPAN
# 'usage' => $usage[$$self],
# 'command' => $command[$$self],
# );
# $cmdhash{'topic'} = $topic[$$self] if (defined($topic[$$self]));
# $cmdhash{'contexts'} = $contexts[$$self] if (defined($contexts[$$self]));
# $cmdhash{'call_style'} = $call_style[$$self] if (defined($call_style[$$self]));
# $cmdhash{'handler'} = $handler[$$self] if (defined($handler[$$self]));
# $cmdhash{'start'} = $start[$$self] if (defined($start[$$self]));
# $cmdhash{'stop'} = $stop[$$self] if (defined($stop[$$self]));
#
# return ( \%cmdhash );
view release on metacpan or search on metacpan
lib/Aion/Format.pm view on Meta::CPAN
=item * C<Roman::Unicode> use digits ↠(5 000), ↂ (1000), and so on.
=item * C<Acme::Roman> added support roman numerals in perl code (C<< I + II -E<gt> III >>), but use C<+>, C<-> and C<*> operations only.
=item * C<Date::Roman> is Perl OO extension for handling roman style dates, but with arabic numbers (id 3 702).
=item * C<DateTime::Format::Roman> is roman date formatter, but with arabic numbers (5 Kal Jun 2003).
=back
view release on metacpan or search on metacpan
lib/Aion/Fs.pm view on Meta::CPAN
=item * L<Mojo::File> – C<< path($file)-E<gt>extname >>.
=item * L<Path::Util> – C<$filename = basename($dir)>.
=item * L<Parse::Path> – C<< Parse::Path-E<gt>new(path =E<gt> 'gophers[0].food.count', style =E<gt> 'DZIL')-E<gt>push("chunk") >>. Работает Ñ Ð¿ÑƒÑ‚Ñми как Ñ Ð¼Ð°ÑÑивами (C<push>, C<pop>, C<shift>, C<splice>). Так же пÐ...
=back
=head2 transpath ($path?, $from, $to)
view release on metacpan or search on metacpan
t/_parse_xml.t view on Meta::CPAN
main();
__END__
<?xml version="1.0" encoding="UTF-8"?>
<?akado-request A1-B2?>
<?xml-stylesheet type="text/xsl" href="/interface/templates/finance.xsl?C3-D4"?>
<main responseType="accepted" crc="40252555">
<billing income-monthly="0" expense-monthly="484" balance-begin="1936" balance-end="1452" last-day="06.05.2014" request-date="06.05.2014">
<income id="383554863" amount="0" type="1" comment="Датой платежа ÑчитаетÑÑ Ð´Ð°Ñ‚Ð° зачиÑÐ»ÐµÐ½Ð¸Ñ ÑредÑтв на Ваш лицевой Ñчет в ÐКÐДО." description="ПоÑÑ‚ÑƒÐ¿Ð»ÐµÐ½Ð¸Ñ Ð½Ð° Ñчет в...
<expense id="383554875" amount="484" type="2" description="СтоимоÑÑ‚ÑŒ уÑлуг в мае 2014">
<bill id="383554876" parent="383554875" amount="4" description="Ðренда кабельного модема"/>
view release on metacpan or search on metacpan
t/pod-coverage.t view on Meta::CPAN
eval "use Test::Pod::Coverage $min_tpc";
plan skip_all => "Test::Pod::Coverage $min_tpc required for testing POD coverage"
if $@;
# Test::Pod::Coverage doesn't require a minimum Pod::Coverage version,
# but older versions don't recognize some common documentation styles
my $min_pc = 0.18;
eval "use Pod::Coverage $min_pc";
plan skip_all => "Pod::Coverage $min_pc required for testing POD coverage"
if $@;
view release on metacpan or search on metacpan
lib/Akamai/Open/DiagnosticTools.pm view on Meta::CPAN
To initiate diagnostinc actions inside the Akamai network, you'll
need the information about the locations from which diagnostic
actions are available.
I<locations()> provides the informations. On success it returns a
Perl-style array reference. On error it returns I<undef> and sets
the I<last_error()> appropriate.
=head2 $diag->mtr($hash_ref)
I<mtr()> returns a network trace like the well know I<mtr> Unix command.
I<mtr()> accepts the following parameters in $hash_ref as a Perl-style
hash reference:
=over 4
=item * destinationDomain
lib/Akamai/Open/DiagnosticTools.pm view on Meta::CPAN
A Akamai Server IP you want to run mtr from. This paramter is optional.
Either location or sourceIp has to be passed to I<mtr()>
=back
On success it returns a Perl-style hash reference. On error it returns
I<undef> and sets the I<last_error()> appropriate.
The hash reference has the following format:
{
lib/Akamai/Open/DiagnosticTools.pm view on Meta::CPAN
=head2 $diag->dig($hash_ref)
I<dig()> returns dns information like the well know I<dig> Unix command.
I<dig()> accepts the following parameters in $hash_ref as a Perl-style
hash reference:
=over 4
=item * hostname
lib/Akamai/Open/DiagnosticTools.pm view on Meta::CPAN
A Akamai Server IP you want to run dig from. This paramter is optional.
Either location or sourceIp has to be passed to I<dig()>
=back
On success it returns a Perl-style hash reference. On error it returns
I<undef> and sets the I<last_error()> appropriate.
The hash reference has the following format:
{
view release on metacpan or search on metacpan
lib/Album.pm view on Meta::CPAN
The album will be organised as follows:
index.html first or only index page
indexN.html subsequent index pages (N = 1, 2, ...)
icons/ directory with navigation icons
css/ directory with stylesheets
large/ original (large) images, with HTML pages
medium/ optional medium sized images, with HTML pages
thumbnail/ thumbnail images
Each image can be labeled with a description, a tag (applies to a
view release on metacpan or search on metacpan
bin/analogize.pl view on Meta::CPAN
path to the file containing the examplar/training data
=item C<project>
path to an AM::Parallel-style project (ignores 'outcome' file); this
should be a directory containing a file called C<data> containing known
exemplars and C<test> containing test exemplars. If the C<test> file does
not exist, then a leave-one-out scheme is used for testing using the
exemplars in the C<data> file.
view release on metacpan or search on metacpan
of F<ppport.h> if you intend to be backward compatible only
down to a certain Perl version.
=head2 --cplusplus
Usually, F<ppport.h> will detect C++ style comments and
replace them with C style comments for portability reasons.
Using this option instructs F<ppport.h> to leave C++
comments untouched.
=head2 --quiet
}
}
if ($cppc) {
my $s = $cppc != 1 ? 's' : '';
warning("Uses $cppc C++ style comment$s, which is not portable");
}
my $s = $warnings != 1 ? 's' : '';
my $warn = $warnings ? " ($warnings warning$s)" : '';
info("Analysis completed$warn");