Result:
found more than 994 distributions - search limited to the first 2001 files matching your query
( run in 1.088 )
Acme-MyFirstModule-JWKEENE
view release on metacpan or search on metacpan
that should be provided before the module is installed.
A README file is required for CPAN modules since CPAN extracts the README
file from a module distribution so that people browsing the archive
can use it to get an idea of the module's uses. It is usually a good idea
to provide version information here so that people can decide whether
fixes for the module are worth downloading.
INSTALLATION
Acme-MyFirstModule-NANDO
view release on metacpan or search on metacpan
that should be provided before the module is installed.
A README file is required for CPAN modules since CPAN extracts the README
file from a module distribution so that people browsing the archive
can use it to get an idea of the module's uses. It is usually a good idea
to provide version information here so that people can decide whether
fixes for the module are worth downloading.
INSTALLATION
Acme-MyFirstModule-RAYMONDJM
view release on metacpan or search on metacpan
A README file is required for CPAN modules since CPAN extracts the
README file from a module distribution so that people browsing the
archive can use it get an idea of the modules uses. It is usually a
good idea to provide version information here so that people can
decide whether fixes for the module are worth downloading.
INSTALLATION
To install this module type the following:
Acme-MyFirstModule-SADAMS
view release on metacpan or search on metacpan
that should be provided before the module is installed.
A README file is required for CPAN modules since CPAN extracts the README
file from a module distribution so that people browsing the archive
can use it to get an idea of the module's uses. It is usually a good idea
to provide version information here so that people can decide whether
fixes for the module are worth downloading.
INSTALLATION
Acme-MyFirstModule-Tracers
view release on metacpan or search on metacpan
A README file is required for CPAN modules since CPAN extracts the
README file from a module distribution so that people browsing the
archive can use it get an idea of the modules uses. It is usually a
good idea to provide version information here so that people can
decide whether fixes for the module are worth downloading.
INSTALLATION
To install this module type the following:
Acme-MyFirstModule-WWILLIS
view release on metacpan or search on metacpan
that should be provided before the module is installed.
A README file is required for CPAN modules since CPAN extracts the README
file from a module distribution so that people browsing the archive
can use it get an idea of the modules uses. It is usually a good idea
to provide important information here so that people can decide whether
fixes for the module are worth downloading.
INSTALLATION
To install this module, run the following commands:
Acme-MyFirstModule-ddeimeke
view release on metacpan or search on metacpan
that should be provided before the module is installed.
A README file is required for CPAN modules since CPAN extracts the README
file from a module distribution so that people browsing the archive
can use it to get an idea of the module's uses. It is usually a good idea
to provide version information here so that people can decide whether
fixes for the module are worth downloading.
INSTALLATION
Acme-MyPeek
view release on metacpan or search on metacpan
- Add a .gitignore file
- Changelog dates are better written as YYYY.MM.DD and probably ordered in
the other, descending, direction
Remark: I have decided to follow the ISO 8601 standard at
http://www.w3.org/TR/NOTE-datetime
- Just use a Makefile.PL and not a Build.PL the latter does not have any
added value any more
- In Makefile.PL ==> meta files link to repository
Acme-NabeAtzz
view release on metacpan or search on metacpan
inc/Module/Install.pm view on Meta::CPAN
use strict 'vars';
use vars qw{$VERSION};
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 = '0.75';
Acme-NameGen
view release on metacpan or search on metacpan
lib/Acme/NameGen.pm view on Meta::CPAN
'fervent', 'festive', 'flamboyant', 'focused',
'friendly', 'frosty', 'gallant', 'gifted',
'goofy', 'gracious', 'happy', 'hardcore',
'heuristic', 'hopeful', 'hungry', 'infallible',
'inspiring', 'jolly', 'jovial', 'keen',
'kind', 'laughing', 'loving', 'lucid',
'mystifying', 'modest', 'musing', 'naughty',
'nervous', 'nifty', 'nostalgic', 'objective',
'optimistic', 'peaceful', 'pedantic', 'pensive',
'practical', 'priceless', 'quirky', 'quizzical',
'relaxed', 'reverent', 'romantic', 'sad',
Acme-NewMath
view release on metacpan or search on metacpan
A README file is required for CPAN modules since CPAN extracts the
README file from a module distribution so that people browsing the
archive can use it get an idea of the modules uses. It is usually a
good idea to provide version information here so that people can
decide whether fixes for the module are worth downloading.
INSTALLATION
To install this module type the following:
Acme-OCEORA-Utils
view release on metacpan or search on metacpan
that should be provided before the module is installed.
A README file is required for CPAN modules since CPAN extracts the README
file from a module distribution so that people browsing the archive
can use it to get an idea of the module's uses. It is usually a good idea
to provide version information here so that people can decide whether
fixes for the module are worth downloading.
INSTALLATION
Acme-OneHundredNotOut
view release on metacpan or search on metacpan
OneHundredNotOut.pm view on Meta::CPAN
referring to memory locations directly in an extremely high-level
language was a dangerous and silly thing to do, and actually used the
damned thing, and I started getting requests for support for it. Then at
some point in 2001, when I should really have known better, I developed
an interest in Microsoft's .NET and the C# language, which I still think
is pretty neat; but I decided it might be a good idea to translate the
Mono project's tokenizer and parser into Perl, ending up with
L<C::Sharp>. I never got around to doing the parser part, or indeed
anything else with it, and so it died a lonely death in a dark corner of
CPAN. L<GTK::HandyClist> was my foray into programming graphical
applications, which started and ended there. L<Bundle::SDK::SIMON> was
OneHundredNotOut.pm view on Meta::CPAN
Finally, I got into web display of archived email, and needed a way of
displaying threads. Amazingly, nobody had coded up JWZ's mail threading
algorithm in Perl yet, so I did that too: L<Mail::Thread>.
But then I decided that C<Mail::*> was in a very sick state. I had been
working with the mail handling modules from CPAN - including my own -
and grown to hate them; they were all too slow, too complicated, too
buggy or all three. It was time for action, and the Perl Email Project
was born.
OneHundredNotOut.pm view on Meta::CPAN
It was only when I got back from Japan that I learnt to play Go. How
stupid was that. For a year I had access to some of the best Go clubs
and professional teacher and players in the world, and then I only pick
the bloody game up when I get back to England. Anyway, any computer
programmer who learns to play go, and they all do soon or later,
eventually decides to do something about the pitiful state of computer
Go. It's quite ridiculous that the game's been around for thousands of
years and the best computer programs we've devised regularly get beaten
resoundingly by small children. Anyway, I did my bit, producing
L<Games::Go::GMP> and L<Games::Go::SGF> as utility libraries, before
working on L<Games::Goban> to represent the state of the game.
OneHundredNotOut.pm view on Meta::CPAN
mainly I haven't had the time to do interesting user-facing stuff on top
of it so that it can be shown off. I tried porting C<Parse::RecDescent>
to it (using L<Parse::RecDescent::Deparse> to figure out what C<P::RD>
was doing) to produce a much faster recursive descent parser, but when I
heard that Damian Conway was funded to work on C<Parse::FastDescent> and
C<Parse::Perl>, (yes, I have a prototype of that too) I decided to leave
him to it. After all, why should I do the work and have other people get
paid for it? These modules did not materialise, but then, a failure on
his part does not constitute necessity on mine.
While I was messing with Parrot, I wanted to get other languages running
Acme-Opish
view release on metacpan or search on metacpan
lib/Acme/Opish.pm view on Meta::CPAN
More accurately, this means, add an arbitrary prefix to the vowel
groups of words, except for the "silent e" and "starting, non-vowel
y's".
Note: This module capitalizes words like you would expect. Maybe a
couple examples will elucidate this point:
enop('Abc') produces 'Opabc'
enop('abC') produces 'opabC'
Unfortunately, this function, currently converts consecutive spaces
Acme-Oppai
view release on metacpan or search on metacpan
A README file is required for CPAN modules since CPAN extracts the
README file from a module distribution so that people browsing the
archive can use it get an idea of the modules uses. It is usually a
good idea to provide version information here so that people can
decide whether fixes for the module are worth downloading.
INSTALLATION
To install this module type the following:
Acme-PDF-rescale
view release on metacpan or search on metacpan
name: Acme-PDF-rescale
version: 0.2
version_from: lib/Acme/PDF/rescale.pm
installdirs: site
requires:
Getopt::Lucid: 0.16
distribution_type: module
generated_by: ExtUtils::MakeMaker version 6.30_01
Acme-PM-Barcelona
view release on metacpan or search on metacpan
lib/Acme/PM/Barcelona/12x5_ca.pod view on Meta::CPAN
print $fila, " ", $resultat[ int rand 3 ], "\n";
}
=head3 Però potser no volem que ho sigui
En canvi, la seva dona vol poder decidir quin resultat tindrÃ
el seu equip favorit. Aixà doncs, cal una llista de resultats
desitjats:
@resultat = ( 1, 'X', 2 );
%quiniela = (
lib/Acme/PM/Barcelona/12x5_ca.pod view on Meta::CPAN
maximum tum val inquementum tum biguttam tum stadium egresso scribe.
vestibulo perlegementum da meo maximo .
maximum tum novumversum egresso scribe.
da II tum maximum conscribementa meis listis.
dum damentum nexto listis decapitamentum fac sic
lista sic hoc tum nextum recidementum cis vannementa da listis.
next tum biguttam tum stadium tum nextum tum novumversum
scribe egresso.
cis
=head3 Don::Mendo
Acme-PM-Berlin-Meetings
view release on metacpan or search on metacpan
lib/Acme/PM/Berlin/Meetings/History.pod view on Meta::CPAN
gegenueber vom Bundeskanzleramt) S-Hauptbahnhof
BBBike-Route
L<http://bbbike.de/cgi-bin/bbbike.cgi?zielname=Elisabeth-Abegg-Str> -
Google Maps
L<http://maps.google.com/maps?oe=utf-8&client=firefox-a&ie=UTF8&q=zollpackhof&fb=1&hq=zollpackhof&cid=0,0,16858087506954263585&ei=X-lPTMjCC-LGOKeZmb8B&ved=0CBoQnwIwAQ&hnear=&ll=52.519459,13.380876&spn=0.028699,0.03047&z=15>
L<geo:52.521293,13.367068>
=head2 Treffen im Juni 2010
Acme-POE-Tree
view release on metacpan or search on metacpan
lib/Acme/POE/Tree.pm view on Meta::CPAN
);
$tree->run();
=head2 run
Run the tree until the user decides they've had enough.
=head1 AUTHOR
Rocco Caputo <rcaputo@cpan.org> with debugging and feedback from
irc.perl.org channel #poe.
Acme-PPIx-MetaSyntactic
view release on metacpan or search on metacpan
lib/Acme/PPIx/MetaSyntactic.pm view on Meta::CPAN
}
}
for my $qq (@{ $self->document->find("PPI::Token::Quote") || [] })
{
# A string that "co-incidentally" happens to have the name as a locally
# defined sub. This might be a __PACKAGE__->can("foo"), so change it!
#
if ($ls->{$qq->string})
{
my $txt = "$qq";
Acme-PSON
view release on metacpan or search on metacpan
inc/Module/Install.pm view on Meta::CPAN
use strict 'vars';
use vars qw{$VERSION};
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 = '0.68';
Acme-Pano-Util
view release on metacpan or search on metacpan
that should be provided before the module is installed.
A README file is required for CPAN modules since CPAN extracts the README
file from a module distribution so that people browsing the archive
can use it to get an idea of the module's uses. It is usually a good idea
to provide version information here so that people can decide whether
fixes for the module are worth downloading.
INSTALLATION
Acme-People-Happy
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.19';
Acme-Perl-Consensual
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';
Acme-Perl-VM
view release on metacpan or search on metacpan
inc/Module/Install.pm view on Meta::CPAN
use strict 'vars';
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 = '0.91';
Acme-PerlML
view release on metacpan or search on metacpan
inc/Module/Install.pm view on Meta::CPAN
use strict 'vars';
use vars qw{$VERSION};
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 = '0.62';
Acme-Pi-Abrahamic
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';
Acme-Pills
view release on metacpan or search on metacpan
lib/Acme/Pills.pm view on Meta::CPAN
that we shall not dignify any further.
=item C<breaks_when_needed>
The third claim is that our products somehow detect your hour of need and
suddenly fail to work immediately. This is clearly a coincidence; our minds
love to see patterns even when they are not present. Think of all of the times
ourproducts have worked perfectly and you will see that, even if our products
ever broke, you merely see coincidences.
=item C<empty_box>
One particularly disturbing claim is that we occasionally ship empty boxes. If
this ever happens, please return the box for a full one.
Acme-Pinoko
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';
Acme-PlayCode
view release on metacpan or search on metacpan
that should be provided before the module is installed.
A README file is required for CPAN modules since CPAN extracts the README
file from a module distribution so that people browsing the archive
can use it to get an idea of the module's uses. It is usually a good idea
to provide version information here so that people can decide whether
fixes for the module are worth downloading.
INSTALLATION
( run in 1.088 second using v1.01-cache-2.11-cpan-4505f990765 )