On Thu, Jun 02, 2005 at 06:57:24PM +0200, David Landgren wrote:
> >My understanding is that inclusion on the Phalanx 100 doesn't constitute
> >any sort of endorsement of the modules. It's hopefully a statement that
> >the module is widely used, but not a judgment on whether it ought to be.
>
>
On Thu, Jun 02, 2005 at 06:48:30AM -0400, Dave Paris ([EMAIL PROTECTED]) wrote:
> It was brought to my attention that Crypt::DES is included in the
> Phalanx 100 list. While I'm flattered, I think this should be replaced
> by a better symmetrical crypto module like Crypt::Rijndael.
Don't be fla
Kevin Scaldeferri wrote:
My understanding is that inclusion on the Phalanx 100 doesn't constitute
any sort of endorsement of the modules. It's hopefully a statement that
the module is widely used, but not a judgment on whether it ought to be.
They are not endorsed, but they are considered "im
On Jun 2, 2005, at 3:48 AM, Dave Paris wrote:
Greetings,
It was brought to my attention that Crypt::DES is included in the
Phalanx 100 list. While I'm flattered, I think this should be
replaced by a better symmetrical crypto module like Crypt::Rijndael.
The reasoning is simple. Crypt::DE
Walter Goulet wrote:
Looks like the phalanx kwiki as well as the phalanx subversion
repository is down.
Any ETA on when it will be back up?
I can get the repository but not the kwiki. But, IIRC, the kwiki is
hosted by Ingy and is physically independent of the repository, which I
believe is hos
Selon Gabor Szabo <[EMAIL PROTECTED]>:
> > So I guess my question is, what exactly am I supposed to do to improve
> > test coverage? Am I supposed to modify the existing scripts so they
> > execute more functions exported by the module? Are any of the other
> > modules currently being tested not u
Gabor Szabo wrote:
On Wed, 30 Mar 2005 21:45:23 -0600, Walter Goulet <[EMAIL PROTECTED]> wrote:
Hi,
Ok, so I've been trying to get started with testing Net-SSLeay for the
Phalanx project. Now the problem I've been having is getting my arms
around how to improve the coverage of the tests included
On Wed, 30 Mar 2005 21:45:23 -0600, Walter Goulet <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Ok, so I've been trying to get started with testing Net-SSLeay for the
> Phalanx project. Now the problem I've been having is getting my arms
> around how to improve the coverage of the tests included with that
et started with testing Net-SSLeay for the Phalanx project. Now the
problem I've been having is getting my arms around how to improve the
coverage of the tests included with that module. It doesn't look like
this module uses the t/ framework, rather a series of scripts in a
given subdirectory
Andy Lester wrote:
I've started a new page on the Kwiki to replace the HereToHelp page:
http://phalanx.kwiki.org/index.cgi?TeamsWanted
Here's where I hope people looking for teams, or teams looking for
people, can get together and join forces.
I'll put my hat in the ring, first: I don't want to
"Andy Lester" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> I'll put my hat in the ring, first: I don't want to run a module team,
> but I'm glad to join one.
>
> xoxo,
> Andy
Ditto for me. I am a Perl neophyte but I think this would be a great way to
learn so things about testi
"Andy Lester" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> There's a new Phalanx article on perl.com:
> http://www.perl.com/pub/a/2005/01/13/phalanx.html
>
> Let's hope we get an influx of Hoplites!
>
> xoxo,
> Andy
>
Hey Andy,
I am new to Perl. If you went by the "Perl Medic" bo
Selon Sébastien Aperghis-Tramoni <[EMAIL PROTECTED]>:
> Hello,
>
> Here are the final lists of the modules dependencies. This time I grouped
> the modules by their respective distribution name.
I forgot to say that these lists were made by reading the META.yml when
available, or by parsing Makefi
Hi!
On Mon, Dec 27, 2004 at 12:33:36AM +0100, S?bastien Aperghis-Tramoni wrote:
> Oops! I didn't include the list on my first reply.
> But on the other hand I have completed the analysis. So here is the
> final list:
> http://rafb.net/paste/results/p4hveb43.html
I haven't got any time in the
Oops! I didn't include the list on my first reply.
But on the other hand I have completed the analysis. So here is the
final list:
http://rafb.net/paste/results/p4hveb43.html
Michael G Schwern wrote:
On Sat, Dec 25, 2004 at 11:04:15PM -0600, Andy Lester wrote:
I'm working on an article for perl
On Sat, Dec 25, 2004 at 11:04:15PM -0600, Andy Lester wrote:
> I'm working on an article for perl.com on the Phalanx project. Those of
> you involved, can you please give a summary of what you've done? Or
> better yet, give me a summary and update the wiki as well?
Don't know if you saw Maddingu
On Mon, Dec 06, 2004 at 02:27:47AM +, Mark Stosberg ([EMAIL PROTECTED])
wrote:
> On 2004-12-02, Andy Lester <[EMAIL PROTECTED]> wrote:
> > I've reorganized all the trees in http://svn.perl.org/phalanx. A
> > description of how things should be is at
> > http://svn.perl.org/phalanx/structure.p
On 2004-12-02, Andy Lester <[EMAIL PROTECTED]> wrote:
> I've reorganized all the trees in http://svn.perl.org/phalanx. A
> description of how things should be is at
> http://svn.perl.org/phalanx/structure.pod.
I think I missed something. This clearly has something to do with SVN
hosting and the P
On Mon, Aug 30, 2004 at 01:15:32PM -0700, Jim Keenan ([EMAIL PROTECTED]) wrote:
> On this page at the Phalanx web site
> (http://qa.perl.org/phalanx/distros.html), it is
> stated, "[the Phalanx 100] should NOT contain any
> modules that are part of core Perl. Those will be
> handled in a different
On Thu, Aug 05, 2004 at 11:51:09PM -0500, Andy Lester wrote:
> It'd be swell if someone generated Devel::Cover dumps for the
> Phalanx 100. Like http://pjcj.sytes.net/cpancover/ but for
> http://qa.perl.org/phalanx/distros.html.
It would be nice if anyone doing the Class::DBI one made sure that t
>> I just ran into a similar "problem" in POE::Driver::SysRW. For
>> portability I have a couple lines similar to
>>
>> $! = 0 if $! == EAGAIN or $! == EWOULDBLOCK;
>>
>> EAGAIN and EWOULDBLOCK are identical on most systems. In fact, one is
>> usually defined in terms of the other. They dif
Rocco Caputo wrote:
On Sun, Jul 11, 2004 at 10:09:38PM +0200, James Mastros wrote:
All unreachable code is either people misusing the term "unreachable", a
bug in Devel::Cover, or dead code that should be removed.
Here's a puzzle, then.
I just ran into a similar "problem" in POE::Driver::SysRW. F
On Sun, Jul 11, 2004 at 10:09:38PM +0200, James Mastros wrote:
>
> All unreachable code is either people misusing the term "unreachable", a
> bug in Devel::Cover, or dead code that should be removed.
Here's a puzzle, then.
I just ran into a similar "problem" in POE::Driver::SysRW. For
portabil
On Jul 11, 2004, at 4:09 PM, James Mastros wrote:
package Foo;
sub new {
my $class=shift;
$class=ref($class)||$class;
bless [], $class;
}
eval { Foo::new(); }
is($!, "new dies when called as a function");
Actually this doesn't die, it does even worse, given this code:
package Foo;
sub new {
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
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
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
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
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
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 a
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
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
Michael G Schwern wrote:
Test coverage is a useful *heuristic* for test effectiveness. Like all
heuristics if you push it too far it falls apart. Get as close to 100% as
is useful and don't worry about the rest.
Indeed. Brian Marick wrote a great paper on this topic - "How to Misuse
Code Covera
On 7/9/2004 4:57 PM, Paul Johnson wrote:
> On Fri, Jul 09, 2004 at 12:10:52PM -0500, Pete Krawczyk wrote:
>
>> Consider [code with unreachable path] Devel::Cover will always see that as
>> a partial test, and never a full test: Is that a bug, then?
That's for you to decide. The lack of coverage s
On Fri, Jul 09, 2004 at 12:10:52PM -0500, 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::C
On Fri, Jul 09, 2004 at 06:31:09PM -0400, Michael G Schwern wrote:
> Looking through a coverage analysis I just ran, here's some more idioms
> that trip up 100% coverage.
>
> my $foo = $bar || '';
>
> my $foo = $bar || 1;
>
> $this || return;
>
> Basically anything of the "$f
On Fri, Jul 09, 2004 at 05:06:09PM -0500, Andy Lester wrote:
> > There's a whole set of these sort of problems.
Looking through a coverage analysis I just ran, here's some more idioms
that trip up 100% coverage.
my $foo = $bar || '';
my $foo = $bar || 1;
$this || retu
* Pete Krawczyk <[EMAIL PROTECTED]> [2004-07-09T13:10:52]
>
> Devel::Cover will always see that as a partial test, and never a full
> test:
> [ ... ]
> Is that a bug, then? Or is it something else? And how should I notate
> that, keeping in mind the goals of Phalanx, so that it's clearly visibl
On Fri, Jul 09, 2004 at 12:10:52PM -0500, 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::Co
> There's a whole set of these sort of problems.
>
> sub new {
> my $proto = shift;
> my $class = ref $proto || $proto;
In this case, we probably don't want that ANYWAY. That's what I did
when I was through Data::Page for Leon Brocard, and it's now at 100%
coverage, across the
On Wed, Oct 29, 2003 at 12:38:31PM -0600, Andy Lester wrote:
> >1) DBI (Tim Bunce specifically asked for help in re-designing the test
> > suite).
> >
> >2) CPANPLUS.
> >
> >3) Module::Build.
>
> I'm all for having those biggies handled by Phalanx, and handled well.
> That's why I'd like to ho
> Ottawa eh? Well, if the infamous `/anick is involved, I'm
> sure we are all
> in for a lot of fun. ;-)
I don't know if he will be. His name usually comes up once every other
meeting or so, but nobody who goes to the meetings has actually seen him in
real life! Sort of like the Yeti, except rea
While Andy would certainly be the best person to answer this, I rather
like the idea of an entire
Perl Mongers group becoming a hoplite. I can't help but wonder if a
little friendly competition
amongst groups might be a wonderful thing. Who can get the most
modules tested?
I agree entirely. W
1) DBI (Tim Bunce specifically asked for help in re-designing the test
suite).
2) CPANPLUS.
3) Module::Build.
I'm all for having those biggies handled by Phalanx, and handled well.
That's why I'd like to hold off on the top two tiers at
http://qa.perl.org/phalanx/distros.html until we get so
--- "Jeays, Mark" <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I'm writing on behalf of Ottawa Perl Mongers. At our last meeting, one of
> our members gave us a quick introduction to the Phalanx project and its
> goals. A number of the members were interested in the idea and we have been
> looking for a
"Jeays, Mark" wrote:
> Hi,
>
> I'm writing on behalf of Ottawa Perl Mongers. At our last meeting, one of
> our members gave us a quick introduction to the Phalanx project and its
> goals. A number of the members were interested in the idea and we have been
> looking for a group project. How would
On Tue, Oct 28, 2003 at 08:03:58AM -0600, Andy Lester wrote:
> On Tue, Oct 28, 2003 at 11:24:51AM +, Tim Bunce ([EMAIL PROTECTED]) wrote:
> > I'd be very happy if you could find someone willing to rework,
> > and ideally then extend, the DBI test suite. Parts of it date back
> > to before perl
I'd be very happy if you could find someone willing to rework,
and ideally then extend, the DBI test suite. Parts of it date back
to before perl 5.0 was released :)
Tim.
On Sun, Oct 12, 2003 at 10:42:36PM -0500, Andy Lester wrote:
> We've got a couple new hoplites out there, so check out the stat
On Tue, Oct 28, 2003 at 11:24:51AM +, Tim Bunce ([EMAIL PROTECTED]) wrote:
> I'd be very happy if you could find someone willing to rework,
> and ideally then extend, the DBI test suite. Parts of it date back
> to before perl 5.0 was released :)
That is indeed a goal. We're holding off on the
Hi!
On Fri, Oct 17, 2003 at 09:42:21PM -, Rafael Garcia-Suarez wrote:
> Thomas Klausner wrote in perl.qa :
> >
> > Well, here's a list of lowercase dist on CPAN (238 dists). Quite a lot of
> > those are in fact real distributions (eg. perl, parrot). In fact I think
> > that perl itself should
At 23:20 +0200 10/17/03, Thomas Klausner wrote:
On Fri, Oct 17, 2003 at 10:09:04PM +0100, Nicholas Clark wrote:
> Something I'd be curious about:
> Modules with lower case names which aren't pragmas.
> (although how you determine this is hard)
Well, here's a list of lowercase dist on CPAN (238
Thomas Klausner wrote in perl.qa :
>
> Well, here's a list of lowercase dist on CPAN (238 dists). Quite a lot of
> those are in fact real distributions (eg. perl, parrot). In fact I think
> that perl itself shouldn't be part of CPANTS
>
> I've no clue on how to figure out if something is a pragm
Hi!
On Fri, Oct 17, 2003 at 10:09:04PM +0100, Nicholas Clark wrote:
> Something I'd be curious about:
> Modules with lower case names which aren't pragmas.
>
> (although how you determine this is hard)
Well, here's a list of lowercase dist on CPAN (238 dists). Quite a lot of
those are in fact
On Mon, Oct 13, 2003 at 10:28:29AM +0200, Thomas Klausner wrote:
> Obviously, this list is far from complete, which is why I request some
> feedback on more hints for Kwalitee from all of you!
Something I'd be curious about:
Modules with lower case names which aren't pragmas.
(although how you
On 16 October 2003 05:47 Robert Spier wrote:
>> Yes. We've been thinking about this. It either needs stealing buildd
>> from Debian, having a box we don't mind destroying every so often, or
>> having a VMware virtual machine we can undo easily. What we need is
>> more free time ;-)
>>
>
> User
> Yes. We've been thinking about this. It either needs stealing buildd
> from Debian, having a box we don't mind destroying every so often, or
> having a VMware virtual machine we can undo easily. What we need is
> more free time ;-)
>
User Mode Linux (limiting to Linux, of course) might be a lig
On Wed, Oct 15, 2003 at 10:34:19PM -, Rafael Garcia-Suarez wrote:
> Michael G Schwern wrote in perl.qa :
> > This all suggests another check: stray files. Emacs backup files. CVS
> > directories. Empty directories. #...# backup files. Makefiles shipped
> > with Makefile.PL, Build and _buil
Michael G Schwern wrote in perl.qa :
> This all suggests another check: stray files. Emacs backup files. CVS
> directories. Empty directories. #...# backup files. Makefiles shipped
> with Makefile.PL, Build and _build shipped with Build.PL, blib/...
In other words, the contents of the default
On Wed, Oct 15, 2003 at 11:53:45AM +0200, Thomas Klausner wrote:
> > configure?
>
> there are currently 4 dists on CPAN that only include a configure script
> (makepp-1.19, glist-0.9.17a10, swig1.1p5, shufflestat-0.0.3)
configure's an alien idiom on CPAN. If its found, I think it should be
eval
On Wed, Oct 15, 2003 at 12:09:05PM +0200, Rafael Garcia-Suarez wrote:
> Thomas Klausner wrote:
> > there are currently 4 dists on CPAN that only include a configure script
> > (makepp-1.19, glist-0.9.17a10, swig1.1p5, shufflestat-0.0.3)
> >
> > 179 do not include any of Makefile.PL, Build.PL or c
Hi!
On Wed, Oct 15, 2003 at 03:24:22PM +0100, Leon Brocard wrote:
> Thomas Klausner sent the following bits through the ether:
>
> > OTOH, it might be an interesting idea to allow CPANTS to compile code (and
> > thus use stuff like Devel::Cover) if not testing the whole of CPAN, but
> > "linting"
On Wed, Oct 15, 2003 at 02:10:46PM +0200, Rafael Garcia-Suarez wrote:
> Nick Ing-Simmons <[EMAIL PROTECTED]> wrote:
> > >Could we infer that a distribution that comes with several Makefile.PLs
> > >may have an overcomplicated build process, maybe indicating a low
> > >kwalitee ?
> >
> > Should I i
Rafael Garcia-Suarez <[EMAIL PROTECTED]> writes:
>Nick Ing-Simmons <[EMAIL PROTECTED]> wrote:
>> >Could we infer that a distribution that comes with several Makefile.PLs
>> >may have an overcomplicated build process, maybe indicating a low
>> >kwalitee ?
>>
>> Should I infer that to get Tk's kwali
Thomas Klausner sent the following bits through the ether:
> OTOH, it might be an interesting idea to allow CPANTS to compile code (and
> thus use stuff like Devel::Cover) if not testing the whole of CPAN, but
> "linting" one distribution.
Yes. We've been thinking about this. It either needs stea
On Wednesday, Oct 15, 2003, at 11:09 Europe/London, Rafael
Garcia-Suarez wrote:
Thomas Klausner wrote:
there are currently 4 dists on CPAN that only include a configure
script
(makepp-1.19, glist-0.9.17a10, swig1.1p5, shufflestat-0.0.3)
179 do not include any of Makefile.PL, Build.PL or configu
Nick Ing-Simmons <[EMAIL PROTECTED]> wrote:
> >Could we infer that a distribution that comes with several Makefile.PLs
> >may have an overcomplicated build process, maybe indicating a low
> >kwalitee ?
>
> Should I infer that to get Tk's kwalitee up it should build as a
> one monolithic .so ?
I
Rafael Garcia-Suarez <[EMAIL PROTECTED]> writes:
>Thomas Klausner wrote:
>> there are currently 4 dists on CPAN that only include a configure script
>> (makepp-1.19, glist-0.9.17a10, swig1.1p5, shufflestat-0.0.3)
>>
>> 179 do not include any of Makefile.PL, Build.PL or configure.
>>
>> Quite a l
On Wed, Oct 15, 2003 at 12:03:58PM +0200, Thomas Klausner wrote:
> On Mon, Oct 13, 2003 at 05:53:15PM -, Rafael Garcia-Suarez wrote:
> > use Pod::Coverage ?
>
> As far as I know, Pod::Coverage compiles the module, which makes it not
> suitable for CPANTS.
Afraid so. It's an eventual TODO-lis
Thomas Klausner wrote:
> there are currently 4 dists on CPAN that only include a configure script
> (makepp-1.19, glist-0.9.17a10, swig1.1p5, shufflestat-0.0.3)
>
> 179 do not include any of Makefile.PL, Build.PL or configure.
>
> Quite a lot come with two or three of those files.
Could we infe
Hi!
On Mon, Oct 13, 2003 at 05:53:15PM -, Rafael Garcia-Suarez wrote:
> > * POD/Code ratio (what would be a good measurement?)
>
> use Pod::Coverage ?
As far as I know, Pod::Coverage compiles the module, which makes it not
suitable for CPANTS.
OTOH, it might be an interesting idea to allow
Hi!
On Mon, Oct 13, 2003 at 07:46:02PM +0200, Tels wrote:
> > * POD/Code ratio (what would be a good measurement?)
>
> No. Some _very_ complex code takes little documentation like:
Agreed.
> Probably something like:
>
> *.pm file has more than 1000 lines of code => bad
>
> :-)
CPANTS
Hi!
On Mon, Oct 13, 2003 at 02:57:34AM -0700, Michael G Schwern wrote:
> On Mon, Oct 13, 2003 at 10:28:29AM +0200, Thomas Klausner wrote:
> > * contains files:
> > * Makefile.PL or Build.PL or configure
>
> configure?
there are currently 4 dists on CPAN that only include a configure script
(m
On Tue, Oct 14, 2003 at 01:14:44PM -0700, Randal L. Schwartz wrote:
> Of course, if you have a well-written name/synopsis/author info,
> I guess this is enough. But now we've just shifted the problem.
Well when I initially thought about it I was answering the needs of
someone who wanted to know:
> "Richard" == Richard Clamp <[EMAIL PROTECTED]> writes:
Richard> It pulls out the name, synopsis and author info from the main module,
Richard> mixes in the dependencies from META.yml, and then sprinkles on the
Richard> last few entries from Changes for good measure.
I'm not even sure that t
On Tue, Oct 14, 2003 at 11:49:44AM -0400, Darren Chamberlain wrote:
> I'll concede that they are useless duplication if someone simply does:
>
> perldoc -t Module.pm > README
I find them to be useful duplication, but I truly hate doing that
myself, so this is what I use:
http://unixbeard.net/
* Michael G Schwern [2003-10-14 08:27]:
> On Mon, Oct 13, 2003 at 10:28:29AM +0200, Thomas Klausner wrote:
> > * README
>
> Personally, I find READMEs useless duplication. Even more so now that
> search.cpan.org works so well.
I'll concede that they are useless duplication if someone simply d
-BEGIN PGP SIGNED MESSAGE-
Moin,
On Monday 13 October 2003 10:28, Thomas Klausner wrote:
> Hi!
> * POD/Code ratio (what would be a good measurement?)
No. Some _very_ complex code takes little documentation like:
=head2 sub delete_first_n_entries($N)
Deletes the first N
On Mon, Oct 13, 2003 at 06:51:43PM +0200, Tels wrote:
> > > * t/* or test.pl
> >
> > test.pl is not a good thing. It doesn't get parsed by "make test". It
> > just runs and spits the output to the screen. If a test fails, "make test"
> > will still succeed. Still, its better than nothing at a
Thomas Klausner wrote in perl.qa :
>
> Hints that were in Leon's last release, but which I didn't port up to now:
> * POD errors
> * POD/Code ratio (what would be a good measurement?)
use Pod::Coverage ?
> * testers results
> * number of releases
-BEGIN PGP SIGNED MESSAGE-
Moin,
On Monday 13 October 2003 11:57, Michael G Schwern wrote:
> On Mon, Oct 13, 2003 at 10:28:29AM +0200, Thomas Klausner wrote:
> > * contains files:
> > * Makefile.PL or Build.PL or configure
>
> configure?
>
> > * README
>
> Personally, I find READMEs u
On Mon, Oct 13, 2003 at 10:28:29AM +0200, Thomas Klausner wrote:
> * contains files:
> * Makefile.PL or Build.PL or configure
configure?
> * README
Personally, I find READMEs useless duplication. Even more so now that
search.cpan.org works so well.
> * t/* or test.pl
test.pl is not a go
On Sun, Oct 12, 2003 at 01:08:39PM +, Mark Stosberg wrote:
> I'm excited to see that the Phalanx project is happening.
>
> On the website I see this unfiled item:
>
> "Use Devel::Cover and gconv".
>
> One way that seems useful to use Devel::Cover is to have an automated coverage
> testing s
On Sun, Oct 12, 2003 at 01:08:39PM +, Mark Stosberg wrote:
> A second sticking point could be that code is OS-specific, so it's not ever going
> to get testing by just one build machine.
And also, in the case of things like Class::DBI, have database specific
code in them, that is tested, but c
On Tue 30 Sep 2003 03:57, Andy Lester <[EMAIL PROTECTED]> wrote:
> I've updated http://qa.perl.org/phalanx/. I started a roster page and a
> status, which shows that Shawn Carroll has started working on
> Date::Calc. Shawn, please let me know how many tests were in Date::Calc
FWIW Date::Calc has
Matthew O. Persico <[EMAIL PROTECTED]> writes:
>On Thu, 21 Aug 2003 22:48:11 -0500, Andy Lester wrote:
>[snip]
>>The project page is at http://qa.perl.org/phalanx/. �Please take a
>>look, tell me your thoughts, and if there are any serious ommissions
>>from the Phalanx 100 module list...
>
>Tk?
If
On Thu, 21 Aug 2003 22:48:11 -0500, Andy Lester wrote:
> The project page is at http://qa.perl.org/phalanx/. Please take a
> look, tell me your thoughts, and if there are any serious ommissions
> from the Phalanx 100 module list...
Test::Reporter?
--
Adam J. Foxson
On Thu, 21 Aug 2003 22:48:11 -0500, Andy Lester wrote:
[snip]
>The project page is at http://qa.perl.org/phalanx/. Please take a
>look, tell me your thoughts, and if there are any serious ommissions
>from the Phalanx 100 module list...
Tk?
--
Matthew O. Persico
Hi,
I just start smoke on this "top100" with cpanplus.
Why, as you display docs, bugs and rating, you didn't display link to
cpan testers results ?
Regards,
--
Alain BARBET
On Fri, Aug 22, 2003 at 09:08:51AM -0500, Andy Lester wrote:
> >If we do, then it won't be the Phalanx 100 anymore, will it. :)
> >I'd highly recommend against a naming scheme that limits your
> >implementation.
> >Hard coded constants and all that. :)
>
> How does it limit my implementation? Do
When will all of this phalanxing start? I'm excited about it and I can't
wait to get my hands dirty. Hopefully with school and all I will have time
to help you guys out.
BTW
phalanxing - the action of testing and improving CPAN and Perl. (or
something to that effect)
:-p
~~Andrew
> -Or
On Friday 22 August 2003 15:08, Andy Lester wrote:
> Core modules are phase two because of the Extra Excitement that will
> be caused by mucking with them and pumpking coordination and whatnot.
None of the phalanx 100 depend on any core modules? Or you just plan to deal
with the bare minimum of c
I'll be interested to see how you handle non-Perl dependencies as in
C libraries.
Yeah, me too! :-)
If we do, then it won't be the Phalanx 100 anymore, will it. :)
I'd highly recommend against a naming scheme that limits your implementation.
Hard coded constants and all that. :)
How does it limit
> Net_SSLeay.pm
Just noticed that's a kinda odd name for a distribution that contains
the modules Net::SSLeay and Net::SSLeay::Handle. I wonder why is it
not called Net-SSLeay?
/-\
http://search.yahoo.com.au - Yahoo! Search
- Looking for more? Try the new Yahoo! Search
Hi!
On Thu, Aug 21, 2003 at 10:48:11PM -0500, Andy Lester wrote:
> The Phalanx project has started its rampup to an official
> announcement. Phalanx is going to beef up the tests, coverage and
> docs on Perl and 100 heavily-used modules from CPAN.
Have you got an plans on combining Phalanx and
On Fri 22 Aug 2003 11:16, Michael G Schwern <[EMAIL PROTECTED]> wrote:
> On Thu, Aug 21, 2003 at 10:48:11PM -0500, Andy Lester wrote:
> > The Phalanx project has started its rampup to an official
> > announcement. Phalanx is going to beef up the tests, coverage and
> > docs on Perl and 100 heavi
On Thu, Aug 21, 2003 at 10:48:11PM -0500, Andy Lester wrote:
> The Phalanx project has started its rampup to an official
> announcement. Phalanx is going to beef up the tests, coverage and
> docs on Perl and 100 heavily-used modules from CPAN.
I'll be interested to see how you handle non-Perl d
Andy Lester wrote:
> The Phalanx project has started its rampup to an official
> announcement. Phalanx is going to beef up the tests, coverage and
> docs on Perl and 100 heavily-used modules from CPAN.
>
> The project page is at http://qa.perl.org/phalanx/. Please take a
> look, tell me your
97 matches
Mail list logo
