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
{
"abstract" : "Make a mental note for programming style",
"author" : [
"Adriano R. Ferreira <ferreira@cpan.org>"
],
"dynamic_config" : 1,
"generated_by" : "ExtUtils::MakeMaker version 7.04, CPAN::Meta::Converter version 2.150001",
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
OneHundredNotOut.pm view on Meta::CPAN
they're copies of other modules that claim to be funny. So my
contributions to C<Acme::*> have been deadly serious.
L<Acme::Dot>, for instance, is another example of how much you can warp
Perl's syntax without resorting to source filters. You can call methods
Ruby-style with the dot operator. But it's still the dot operator. You
work that one out.
And my other contribution to C<Acme::*> - and my hundredth module? Well,
you've just finished reading it.
view release on metacpan or search on metacpan
lib/Acme/PERLANCAR/Test/MetaCPAN/HTML/Inline1.pm view on Meta::CPAN
=for html <!-- begin comment --><script>alert("hello");</script><!-- end comment -->
=for html <!-- begin comment --><p>A normal paragraph</p><!-- end comment -->
=for html <!-- begin comment --><style> </style><!-- end comment -->
=for html <div id=#one> inside div </div>
=for html <div class=one> inside div2 </div>
=for html <p style="color: red">A red paragraph</p>
=for html <pre class="line-numbers">foo</pre>
=for html <pre id="source" class="line-numbers">line 1
line 2
lib/Acme/PERLANCAR/Test/MetaCPAN/HTML/Inline1.pm view on Meta::CPAN
Tables allowed.
HTML comments stripped.
<script>, <style> stripped.
<div> allowed but attributes stripped.
=head1 HOMEPAGE
view release on metacpan or search on metacpan
Acme-PIA-Export-0.019.html view on Meta::CPAN
<title>Module Acme::PIA::Export</title>
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<link rev="made" href="mailto:" />
</head>
<body style="background-color: white">
<p><a name="__index__"></a></p>
<!-- INDEX BEGIN -->
<ul>
view release on metacpan or search on metacpan
lib/Acme/PM/Barcelona/12x5_ca.pod view on Meta::CPAN
use strict;
print "Hello, world!\n";
=head3 Acme::Code::FreedomFighter
Defends our right to code in any style waiting for the right
moment to strike back at the evil oppressors.
use Acme::Code::FreedomFicghter;
use Acme::Code::Police;
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/Acme/PPIx/MetaSyntactic.pm view on Meta::CPAN
=over
=item C<< new(%attributes) >>
Moose-style constructor.
=back
=head2 Attributes
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 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
commit 06f2031b62b1651b7d59a914ac97eb2f1932e38d
Author: Rocco Caputo <rcaputo@cpan.org>
Date: Mon Jul 24 22:50:24 2006 +0000
Yaakov suggested that the package name use apostrophe rather than ::
style namespaces. I compromised by having the Aklo version of the
source use it.
==============
End of Excerpt
==============
view release on metacpan or search on metacpan
lib/Acme/ppport.h view on Meta::CPAN
of F<lib/Acme/ppport.h> if you intend to be backward compatible only
down to a certain Perl version.
=head2 --cplusplus
Usually, F<lib/Acme/ppport.h> will detect C++ style comments and
replace them with C style comments for portability reasons.
Using this option instructs F<lib/Acme/ppport.h> to leave C++
comments untouched.
=head2 --quiet
lib/Acme/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
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
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
[](https://travis-ci.org/htk291/p5-Acme-PriPara) [](https://coveralls.io/r...
# NAME
Acme::PriPara - It's new $module
# SYNOPSIS
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/Acme/Pythonic.pm view on Meta::CPAN
return 0 if not defined $proto;
return $proto =~ /^;?&$/;
}
# We follow perlstyle here, as we did until now.
sub cuddle_elses_and_friends {
s/^([ \t]*})\s*(?=(?:elsif|else|continue)\b)/$1 /gm;
s/^([ \t]*})\s*(?=(?:if|unless|while|until|for|foreach)\b(?!.*{$tc?$))/$1 /gm;
}
lib/Acme/Pythonic.pm view on Meta::CPAN
This happens I<before> L<Filter::Simple> undoes the blanking out of
PODs, strings, and regexps. Those parts are marked with the label
C<BLANKED_OUT> for easy identification.
Acme::Pythonic generates human readable Perl following L<perlstyle>, and
tries meticulously to be respectful with the original source code.
Blank lines and comments are preserved.
=head1 BUGS
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/Acme/RPC.pm view on Meta::CPAN
* json will croak if a reference contains objects in side it somewhere. Should handle this gracefully.
* Offer JSON output! Not just Data::Dumper. Do this for action=dump, action=call, and the default tree view.
* If Devel::Leak won't give us refs... have to do an Acme::State style crawl from main::,
but crawling into each sub and looking at its lexicals with PadWalker.
Could make for a nice tree view.
Would also make it easy to filter out the variables that hold refs.
* Maybe this should be called Acme::RPC.
lib/Acme/RPC.pm view on Meta::CPAN
Gives an index of packages, subroutines, variables in those subroutines, closures in those variables, and so on.
=item C<< output=json >>
Output a JavaScript datastructures (JSON) instead of Perl style L<Data::Dumper> or HTML.
The main index page otherwise prints out HTML (under the assumption that a human will be digging through it)
and other things mostly emit L<Data::Dumper> formatted text.
=item C<< oid=(number) >>
lib/Acme/RPC.pm view on Meta::CPAN
my $ob = Devel::Pointer::deref($oid);
my $buf = Data::Dumper::Dumper($ob);
# $buf =~ s{(0x[a-f0-9]{6,})}{<a href="?oid=$1">$1</a>}g;
$request->print(qq{<pre>$buf</pre>\n});
* Accepts posts as well, and handle by data type.
Posts to CODE refs run them with the arguments (attempt to reconstitute object references in the arguments... move to 0x style oids again
to support this).
Posts to object references (blessed things) invoke the named method in them (again, reconstituting the args).
Posts to scalars, arrays, hashes, etc merely replace their data.
view release on metacpan or search on metacpan
lib/Acme/RandomEmoji.pm view on Meta::CPAN
Acme::RandomEmoji - pick an emoji randomly
=head1 SYNOPSIS
=for html
<a href="https://raw.githubusercontent.com/shoichikaji/Acme-RandomEmoji/master/author/screenshot.png"><img src="https://raw.githubusercontent.com/shoichikaji/Acme-RandomEmoji/master/author/screenshot.png" alt="screenshot" style="max-width:100%;"></a>
=head1 DESCRIPTION
Acme::RandomEmoji picks an emoji randomly.
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/Acme/ReturnValue/MakeSite.pm view on Meta::CPAN
sub _html_cool_value {
my ($self, $value, $report, $id) = @_;
my $html;
my $count = @$report;
$html = qq[<tr><td>$count</td><td>$value</td><td><a href="javascript:void(0)" onclick="] . q[$('#]. $id. q[').toggle()">show</td></td></tr>].
qq[<tr id='$id' style='display:none' ><td></td><td colspan=2>];
$html .= join("<br>\n",map { $self->_link_search_package($_->{package}) } sort { $a->{package} cmp $b->{package} } @$report);
$html .= "</td></tr>";
return $html;
}
lib/Acme/ReturnValue/MakeSite.pm view on Meta::CPAN
my $id = $ele->{package};
$id=~s/::/_/g;
$html.="<tr><td colspan width='30%'>".$self->_link_dist($dist)."</td>";
$html.="<td width='69%'>".$ele->{package}."</a></td>".
q{<td width='1%'><a href="javascript:void(0)" onclick="$('#}.$id.q{').toggle()">}."show</td></tr>
<tr id='$id' style='display:none' ><td></td><td colspan=2>".$val."</td></tr>";
}
return $html;
}
sub _link_dist {
lib/Acme/ReturnValue/MakeSite.pm view on Meta::CPAN
return <<"EOHTMLHEAD";
<html>
<head><title>Acme::ReturnValue findings</title>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8">
<script src="jquery-1.3.2.min.js" type="text/javascript"></script>
<link href="acme_returnvalue.css" rel="stylesheet" type="text/css">
</head>
<body>
<h1 id="top">Acme::ReturnValue</h1>
view release on metacpan or search on metacpan
lib/Acme/RightSideOutObject.pm view on Meta::CPAN
Acme::RightSideOutObject work exactly like the inside out object it replaces
except that it is also a hashref full of the object's instance data.
Methods may be called on it.
Options are available, mix and match style:
use Acme::RightSideOutObject 'weaken';
Attempt not to leak so much memory.
lib/Acme/RightSideOutObject.pm view on Meta::CPAN
=head1 BUGS
Leaks memory.
Can't subclass inside out objects with right side out code (but obviously has-a style delegation works).
Should support other flavors of inside out objects than just Class::InsideOut.
Doesn't use the exporter.
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/Acme/RunDoc.pm view on Meta::CPAN
Acme::RunDoc->do("helloworld.doc");
=head1 DESCRIPTION
It is recieved wisdom that word processors are better than text editors.
After all, you can style your documents with different fonts and colours;
you can take advantage of the built-in spell check; and your ugly single
and double quote characters get auto-replaced with "smart" curly versions.
This module allows you to run Perl documents edited in Microsoft Word
(and other word processors capable of saving in the ".doc" format) as
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/Acme/SList/XSLT.pm view on Meta::CPAN
<data>ccc</data>
<data>ddd</data>
</index>
});
my $style_doc = $parser->parse_string(
q{<?xml version="1.0" encoding="iso-8859-1"?>
<xsl:stylesheet version="1.0"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method="xml" indent="yes" encoding="iso-8859-1"/>
<xsl:template match="/">
<html>
<body>
lib/Acme/SList/XSLT.pm view on Meta::CPAN
<p>Test: *** <xsl:value-of select="."/> ***</p>
</xsl:for-each>
</body>
</html>
</xsl:template>
</xsl:stylesheet>
});
my $stylesheet = $xslt->parse_stylesheet($style_doc);
my $results = $stylesheet->transform($source);
print $stylesheet->output_string($results);
=head1 AUTHOR
Klaus Eichner <klaus03@gmail.com>