view release on metacpan or  search on metacpan

lib/Acme/CPANModulesUtil/Bencher.pm  view on Meta::CPAN

                  my $t = Text::ANSITable->new(
                      use_utf8 => 0,
                      use_box_chars => 0,
                      use_color => 0,
                      columns => $table->[0],
                      border_style => 'Default::single_ascii',
                  );
                  $t->add_row($table->[$_]) for 1..@$table-1;
                  $t->draw;
              },

lib/Acme/CPANModulesUtil/Bencher.pm  view on Meta::CPAN

               my $t = Text::ANSITable->new(
                   use_utf8 => 0,
                   use_box_chars => 0,
                   use_color => 0,
                   columns => $table->[0],
                   border_style => 'Default::single_ascii',
               );
               $t->add_row($table->[$_]) for 1..@$table-1;
               $t->draw;
           },
 

 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

FreedomFighter.pm  view on Meta::CPAN

__END__

=head1 NAME

Acme::Code::FreedomFighter - Defends our right to code in any style
waiting for the right moment to strike back at the evil oppressors.

=head1 SYNOPSIS

  #!/usr/bin/perl

 view release on metacpan or  search on metacpan

lib/Acme/Comment.pm  view on Meta::CPAN

            single      => '(?:\*)|(?:&&)',
        }
    };


    ### the comment styles for ADA and Basic are the same ###
    for my $type(qw|ADA|)                               { $Conf->{$type} = $Conf->{'BASIC'} }

    for my $type(qw|POSTSCRIPT|)                        { $Conf->{$type} = $Conf->{'LATEX'} }

    for my $type(qw|ADVSYS LISP SCHEME|)                { $Conf->{$type} = $Conf->{'ORTHOGONAL'} }

lib/Acme/Comment.pm  view on Meta::CPAN

    if(@_%2){
        die "Incomplete set of arguments to $package\n"
    }

    ### see if there are any arguments, if not, we default to the C comment style ###
    if( keys %args ) {

        ### check if the user requested a certain type of comments ###
        if( $args{type} ) {

lib/Acme/Comment.pm  view on Meta::CPAN

                                                ? $args{one_line}
                                                : 0;

        }

    ### no arguments, Let's take the default C comment style ###
    }
}

sub parse {

lib/Acme/Comment.pm  view on Meta::CPAN

Unlike the pseudo multi-line comment C<if (0) {}>, the code being
commented out need not be syntactically valid.

=head1 USE

Acme::Comment contains several different commenting styles.

Styles may be specified by the C<types> argument, or by C<start> and
C<end> and manipulated with C<own_line> and C<one_line>.

Styles may contain multi-line comments and single-line comments.

lib/Acme/Comment.pm  view on Meta::CPAN

You cannot specify both C<type> and C<start> and C<end>, and C<start>
and C<end> must both be provided if you provide one of them.

=head2 types

The C<types> argument specifies what language style should be used.
Only one language style may be specified.

=over 4

=item * Ada

lib/Acme/Comment.pm  view on Meta::CPAN

Single-line comments use either C<==> or C<-->.

=item * C

The default for Acme::Comment is C-style multi-line commenting
with C</*> and C<*/>.  However, if you wish to change C<one_line>
or C<own_line>, you must explicitly specify the type.

=item * C++

C++ multi-line style uses C</*> and C<*/>.  Single-line uses C<//>.

=item * C#

C# multi-line style uses C</*> and C<*/>.  Single-line uses C<//>.

=item * Chill

Multi-line comments use C</*> and C<*/>.

=item * Clean

Clean multi-line style uses C</*> and C<*/>.  Single-line uses C<//>.

=item * E

Single-line comments use C<#>.

lib/Acme/Comment.pm  view on Meta::CPAN

Single-line comments start with C<-->.

=item * Elastic

Elastic multi-line style uses C</*> and C<*/>.  Single-line uses C<//>.

=item * Focal

Single-line comments start with C<comment>.

lib/Acme/Comment.pm  view on Meta::CPAN

Single-line comments use C<!>.

=item * Guile

Guile multi-line style uses C</*> and C<*/>.  Single-line uses C<//>.

=item * Haskell

Single-line comments start with C<-->.

=item * HTML

HTML style has multi-line commenting in the form of C<E<lt>!--> and
C<--E<gt>>.

=item * Hugo

Multi-line comments begin with C<!\> and end with C<\!>.  Single-line

lib/Acme/Comment.pm  view on Meta::CPAN

be preceded by a line number in the following syntax:
C<(23) DO NOTE THAT>.

=item * Java

Java multi-line style uses C</*> and C<*/>.  Single-line uses C<//>.

=item * Joy

Multi-line comments use C<(*> and C<*)>.

lib/Acme/Comment.pm  view on Meta::CPAN

Single-line comments use C<#>.

=item * PHP

PHP multi-line style uses C</*> and C<*/>.  Single-line uses C<//>.

=item * Pilot

Single-line comments in the syntax C<\/\/> are supported.

 view release on metacpan or  search on metacpan

lib/Acme/Constructor/Pythonic.pm  view on Meta::CPAN

__END__

=head1 NAME

Acme::Constructor::Pythonic - import Python-style constructor functions

=head1 SYNOPSIS

    use Acme::Constructor::Pythonic qw(
        LWP::UserAgent

 view release on metacpan or  search on metacpan

inc/IO/Scalar.pm  view on Meta::CPAN

### Stringification, courtesy of B. K. Oxley (binkley):  :-)
use overload '""'   => sub { ${*{$_[0]}->{SR}} };
use overload 'bool' => sub { 1 };      ### have to do this, so object is true!

### The package version, both in 1.23 style *and* usable by MakeMaker:
$VERSION = "2.110";

### Inheritance:
@ISA = qw(IO::Handle);

 view release on metacpan or  search on metacpan

xt/release/pod-coverage.t  view on Meta::CPAN

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

slides/index.html  view on Meta::CPAN

<head>
<title></title>
<meta name="Content-Type" content="text/html; charset=utf-8" />
<meta name="generator" content="Spork v0.20" />
<link rel='icon' href='favicon.png' />
  <link rel="stylesheet" type="text/css" href="" />
<style type="text/css"><!--
/* BEGIN index.css */
hr {
    color: #202040;
    height: 0px;
    border-top: 0px;

slides/index.html  view on Meta::CPAN

    margin-right: 6pt;
}

small {
    font-size: 9pt;
    font-style: italic;
}

#topbar {
    background: lightblue;
    color: blue;

slides/index.html  view on Meta::CPAN

    background-image: url(/logo.png);
    background-repeat: no-repeat;
}
/* END index.css */

--></style>
<script type="text/javascript">
// BEGIN controls.js
function nextSlide() {
    window.location = 'start.html';
}

slides/index.html  view on Meta::CPAN

<!-- BEGIN bottom -->
<div id="bottombar">
<table width="100%">
<tr>
<td align="left" valign="middle">
    <div style="display:none">
    <a accesskey='p' href="">&lt; &lt; Previous</a> |
    <a accesskey='i' href="">Index</a> |
    <a accesskey='n' href="start.html">Next &gt;&gt;</a>
    </div>
</td>

 view release on metacpan or  search on metacpan

README  view on Meta::CPAN

   perl Build.PL
   perl Build
   perl Build test
   perl Build install

If you wish, you may use the old MakeMaker style instead:

   perl Makefile.PL
   make
   make test
   make install

 view release on metacpan or  search on metacpan

TODO  view on Meta::CPAN

fix-up window when font cycling:
       resize && mvwin w/ pre-calc'd vals
       alternate through a set of dup'd wins

Multiple style "delays"?
	cond > 0 ? every(seconds=>cond) : offset = 0

selectively recompile subroutines?
modify $RE{balanced}{-begin=>'sub\s+$NAME.*?{'}{-end=>'}'}

 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

lib/Acme/DeepThoughts.pm  view on Meta::CPAN

When you're riding in a time machine way far into the future, don't stick your elbow out the window, or it'll turn into a fossil.
It takes a big man to cry, but it takes a bigger man to laugh at that man.
One thing kids like is to be tricked. For instance, I was going to take my little nephew to Disneyland, but instead I drove him to an old burned-out warehouse. "Oh, no," I said. "Disneyland burned down." He cried and cried, but I think that deep down...
A good way to threaten somebody is to light a stick of dynamite. Then you call the guy and hold the burning fuse up to the phone. "Hear that?" you say. "That's dynamite, baby."
Why do people in ship mutinies always ask for "better treatment"? I'd ask for a pinball machine, because with all that rocking back and forth you'd probably be able to get a lot of free games.
I'd like to be buried Indian-style, where they put you up on a high rack, above the ground. That way, you could get hit by meteorites and not even feel it.
If I lived back in the Wild West days, instead of carrying a six-gun in my holster, I'd carry a soldering iron. That way, if some smart-aleck cowboy said something like "Hey, look. He's carrying a soldering iron!" and started laughing, and everybody ...
I bet when the Neanderthal kids would make a snowman, someone would always end up saying, "Don't forget the thick, heavy brows." Then they would all get embarrassed because they remembered they had the big hunky brows too, and they'd get mad and eat ...
There should be a detective show called 'Johnny Monkey'. That way every week a criminal could say, "I ain't gonna get caught by no monkey," but then he would, and I don't think I'd ever get tired of that.
Fear can sometimes be a useful emotion. For instance, let's say you're an astronaught on the moon and you fear that your partner has been turned into Dracula. The next time he goes out for the moon pieces, wham! You just slam the door behind him and ...
Too bad you can't buy a voodoo globe so that you could make the earth spin real fast and freak everybody out.

 view release on metacpan or  search on metacpan

lib/Acme/DependOnEverything.pm  view on Meta::CPAN

use Alice;
use Alien;
use Alien::ActiveMQ;
use Alien::Alien;
use Alien::AntTweakBar;
use Alien::astyle;
use Alien::autoconf;
use Alien::automake;
use Alien::Autotools;
use Alien::Base::ModuleBuild;
use Alien::BatToExeConverter;

lib/Acme/DependOnEverything.pm  view on Meta::CPAN

use Module::CGI::Install;
use Module::Changes;
use Module::Changes::ADAMK;
use Module::Check_Args;
use Module::CheckDep::Version;
use Module::Checkstyle;
use Module::CheckVersion;
use Module::Cloud;
use Module::Collect;
use Module::Collection;
use Module::Compile;

lib/Acme/DependOnEverything.pm  view on Meta::CPAN

use Xymon::Server::History;
use Xymon::Server::Status;
use Yahoo::Answers;
use Yahoo::BBAuth;
use Yahoo::CAS;
use Yahoo::Lifestyle;
use Yahoo::Marketing;
use Yahoo::Marketing::APT;
use Yahoo::Music::Ratings;
use Yahoo::Search;
use Yahoo::Weather;

 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

DoubleHelix.pm  view on Meta::CPAN

  use Acme::DoubleHelix;
  print "Hello";

=head1 DESCRIPTION

Acme::DoubleHelix obfuscates codes in Double-helix style. This is inspired by MeowChow's double helix obfuscation at Perlmonks and Conway's Acme::Bleach.

=head1 DIAGNOSTICS

=over 2

 view release on metacpan or  search on metacpan

lib/Acme/Dump/And/Dumper.pm  view on Meta::CPAN

P.S.: eventually I ended up using L<Data::Rmap> instead of the Freezer.

=begin html

<img src="http://zoffix.com/CPAN/Acme-Dump-and-Dumper.jpg"
    style="border: 2px solid #aaa!important; display: block!important; margin: 20px 0!important;"
    alt="Dumb and Dumber">

=end html

=head1 REPOSITORY

 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

lib/Acme/EyeDrops.pm  view on Meta::CPAN

                  Hospel and `/anick; colourful but not very suspenseful
    tpr           Vertical banner of "The Perl Review"
    uml           A UML diagram
    undies        A pair of underpants
    window        A window
    writing_perl  Perl in camel-style by Takanori KAWAI (Japanese)
    yanick        Caricature of `/anick's noggin
    yanick2       Uttered by `/anick during TPR02
    yanick3       Pictorial version of yanick2
    yanick4       Abbreviated version of shape yanick

 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/FSM.pm  view on Meta::CPAN

    $rc = $self->query_rc( @args );
    $rc = $self->verify( $rc, $state, $tag, $subject, $test );

Here comes rationale.
Writing (or should I say "composing"?) correct {fst} B<A::F> style is hard
(I know what I'm talking about, I've made a dozen already).
The purpose of B<verify()> is to check if the I<{fst}> at hands isn't fubar.
Nothing more, nothing less.
B<query_rc()> is a placeholder for one of B<query_.*()> methods,
I<$test> will be matched against C<ref $rc>.

 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

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 $@;