On Sun, Jul 11, 2004 at 12:46:01AM -0400, Michael G Schwern wrote:
> Most modules now have a META.yml file which contains (amongst other things)
> module dependency information. Simplest thing to do would be to make a
> local miniCPAN mirror [1] and walk through the archive files [2] in
> modules
On Jul 10, 2004, at 12:35 PM, Robert Rothenberg wrote:
The reason is that I would like to integreate this with testing
information from the CPAN Testers. So if I find that there are no
testing results for platform 'x' for a specific module, I can check to
see if one of the dependent modules fai
On 7/11/2004 12:46 AM Michael G Schwern wrote:
Most modules now have a META.yml file which contains (amongst other things)
module dependency information. Simplest thing to do would be to make a
local miniCPAN mirror [1] and walk through the archive files [2] in
modules/02packages.details.txt look
On Jul 9, 2004, at 6:06 PM, Andy Lester wrote:
Don't be mesmerized by 100% coverage.
Agreed 100% here. However, I stand by my original statement that you
CAN have 100% coverage on subroutines and pod. Any disagreement on
that
one?
I agree with having 100% on subroutines, and I would add that 100
On Sun, Jul 11, 2004 at 12:26:44PM -0400, stevan little wrote:
> As for POD, in most cases, I agree with you, but to say you should have
> 100% POD coverage brings up several other questions, such as; Should I
> document private methods?
IMPO yes, but Pod::Coverage (and thus Devel::Cover) will
Subject: Re: Phalanx: What if full coverage isn't possible? (fwd)
From: stevan little <[EMAIL PROTECTED]>
Date: Sun, 11 Jul 2004 12:26:44 -0400
}As for POD, in most cases, I agree with you, but to say you should have
}100% POD coverage brings up several other questions, such as; Should I
}docume
Micheal,
On Jul 11, 2004, at 2:09 PM, Michael G Schwern wrote:
On Sun, Jul 11, 2004 at 12:26:44PM -0400, stevan little wrote:
As for POD, in most cases, I agree with you, but to say you should
have
100% POD coverage brings up several other questions, such as; Should I
document private methods?
IMP
On Sun, Jul 11, 2004 at 12:26:44PM -0400, stevan little ([EMAIL PROTECTED]) wrote:
> As for POD, in most cases, I agree with you, but to say you should have
> 100% POD coverage brings up several other questions, such as; Should I
> document private methods? What about modules which are meant to b
On Sun, Jul 11, 2004 at 03:07:22PM -0400, stevan little ([EMAIL PROTECTED]) wrote:
> I think that reg-ex is too loose (and incorrect, but I know you really
> meant /^[A-Z]+$/). I would rather see it check for all the documented
> magic methods rather than a catch all for UPPERCASE names. Even tho
Oh, bother. I think I somehow goofed up the patch part, so here it is
again regenerated. (The pbc files were okay in my original sending.)
nat.pat.gz
Description: GNU Zip compressed data
Jarkko Hietaniemi wrote:
> Oh, bother. I think I somehow goofed up the patch part, so here it is
> again regenerated. (The pbc files were okay in my original sending.)
This is getting embarrassing.
--
Jarkko Hietaniemi <[EMAIL PROTECTED]> http://www.iki.fi/jhi/ "There is this special
biologis
Jarkko Hietaniemi <[EMAIL PROTECTED]> wrote:
> Also, to generate the number_2.pbc I had to compile a new uselongdouble
> Perl in Linux
You don't need that Perl anymore - or shouldn't:
$perl Configure.pl --floatval="long double"
should do it.
> ... and in there I had to #if 0 the below in src
# New Ticket Created by Jarkko Hietaniemi
# Please include the string: [perl #30670]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org:80/rt3/Ticket/Display.html?id=30670 >
In 64-bit environments 20 is not *that* big. Patch attached.
--
Jarkk
# New Ticket Created by Jarkko Hietaniemi
# Please include the string: [perl #30671]
# in the subject line of all future correspondence about this issue.
# http://rt.perl.org:80/rt3/Ticket/Display.html?id=30671 >
I ran into various failures with nci.t and object-meths.t I lack the
time and th
Still a bit lacking, 'specially in the documentation department, but I've
got a version that sucks much less than it did, and is possibly even
correct. (Go figure. Surprised me, too... :)
Anyway, if you want to fiddle,
http://www.sidhe.org/~dan/Python-Bytecode-2.2.tar.gz and have at it. If an
obje
On Jul 11, 2004, at 11:09 AM, Michael G Schwern wrote:
I document private code like this:
=begin private
put your normal POD here
=end private
perldoc won't show the POD but someone reading through the code (and
thus
needing to know about private functions) will see it. And POD is very
readable i
Pete Krawczyk wrote:
Consider the following code:
$impclass ||= implementor($scheme) ||
do {
require URI::_foreign;
$impclass = 'URI::_foreign';
};
That's in URI.pm, lines 54-58.
Devel::Cover treats that as a conditional. So short of deleting
URI::_forei
> : Hello everybody,
> :
> : I'm about to learn myself perl6 (after using perl5 for some time).
>
> I'm also trying to learn perl6 after using perl5 for some time. :-)
I wouldn't even try to compare you and me :-)
> Pretty close. The way it's set up currently, $len is a reference
> to a var
> -Original Message-
> From: Jonadab the Unsightly One [mailto:[EMAIL PROTECTED]
> Austin Hastings <[EMAIL PROTECTED]> writes:
>
> > I think this is something that we'll want as a "mode", a la
> > case-insensitivity. Think of it as "mark insensitivity."
>
> Makes sense to me, but...
>
> >
19 matches
Mail list logo
