Adam Kennedy wrote:
* has_pod_index: The POD contains at least one X<> keyword that helps
POD indexers. Whether only one is usefull is open for debate, because
at least the license (X), your CPAN ID under authors (x),
and some generic keyword what your module (X) is about can
probably added eve
Ian Langworth wrote:
I propose a new Kwalitee metric, released_while_burning_midnight_oil.
Authors who released their modules between 8AM and 1AM the next day
(local time) will be awarded one point. Authors who, despite their
girlfriend's pleading, stay awake at stupid hours of the night to hack
Adrian Howard wrote:
On 8 Jul 2005, at 20:08, Adam Kennedy wrote: [snip]
There's no way to get a listing of the annotations for a given
author id, or even for a given dist. So I'm reduced to manually
looking through a thousand odd web pages to find potential changes
or improvements to the cod
Michael G Schwern wrote:
On Fri, Aug 05, 2005 at 11:32:45AM -0400, Robert wrote:
Is the inline POD the current preferred way?
That really depends on who you ask. Me? I prefer it. Its totally a matter
of style.
Pros:
* Keeps the docs close to the code so you're more likely to keep the d
David Golden wrote:
As a vim user, I found it helpful to edit my perl.vim syntax file like so:
" Use only the bare minimum of rules
- if exists("perl_fold")
+ if exists("perl_fold_pod")
syn region perlPOD start="^=[a-z]" end="^=cut" fold
else
syn region perlPOD start="^=[a-z]" end="^
Smylers wrote:
Ivan Tubert-Brohman writes:
I'm also considering the possibility of sending automated emails,
similar to what rt.cpan.org does. However, I was still unsure about
whether to do it opt-in or opt-out (or no-option ;-).
Opt-out (or no-option) would irritate far too many people
Michael G Schwern wrote:
On Thu, Aug 11, 2005 at 02:49:57PM -0700, Ovid wrote:
BEGIN { use_ok 'Test::Code' or die }
ok defined *::is_code{CODE},
'&is_code should be exported to our namespace';
I usually do this with can_ok()
can_ok( __PACKAGE__, qw(is_code isnt_code) );
Isn'
cpan tester wrote:
I'm not sure where to report this, but there seems to
be a bug in search.cpan.org related to modules
containing scripts with hyphens in them.
You could try http://search.cpan.org/feedback . Whatever you send there
will go into the search.cpan.org request tracking system.
Th
Adam Kennedy wrote:
Only the libraries (and .pod docs) in your dist should be indexed)
things in inc/ and t/ and examples/ etc should NOT be indexed. Thus,
there should be a no_index entry in the meta.yml for all of these
directories (if they have .pm files in them).
Sorry for my ignorance, bu
Hi,
Tels wrote:
Since for security reasons your Perl box is not connected to the net, you
fetch it and all dependencies from CPAN and transfer them via sneaker net
and USB stick. It includes some gems like:
A solution to the sneakernet problem is to have your own CPAN mirror,
either on a mac
Let's play devil's advocate. On the positive side, if you bundle the
testing module, you can be more certain that your tests will work if the
new version of the bundled module breaks backward compatibility, whether
by design or by accident... If I *know* that my module tests properly
with Test:
James E Keenan wrote:
Good point. Modules created with ExtUtils::ModuleMaker, by default,
include a CHANGES file in the distribution. But it's easy to set an
option to include the changes in the HISTORY section of the POD. Someone
who does that should not be viewed as creating a distribution
Randy W. Sims wrote:
Is there a way to make C or C fail without manipulating
@INC or hiding the physical file?
Check out Devel::Hide. I've never used it, but it's supposed to do that.
From the SYNOPSIS:
use Devel::Hide qw(Module/ToHide.pm);
require Module::ToHide; # fails
use Devel::Hi
Randy W. Sims wrote:
Is there a way to make C or C fail without manipulating
@INC or hiding the physical file?
Check out Devel::Hide. I've never used it, but it's supposed to do that.
From the SYNOPSIS:
use Devel::Hide qw(Module/ToHide.pm);
require Module::ToHide; # fails
use Devel::Hi
Tels wrote:
* has_pod_index: The POD contains at least one X<> keyword that helps
POD indexers. Whether only one is usefull is open for debate, because
at least the license (X), your CPAN ID under authors (x),
and some generic keyword what your module (X) is about can
probably added even for the
Adam Kennedy wrote:
* has_pod_index: The POD contains at least one X<> keyword that helps
POD indexers. Whether only one is usefull is open for debate, because
at least the license (X), your CPAN ID under authors (x),
and some generic keyword what your module (X) is about can
probably added eve
16 matches
Mail list logo
