Re: Proposed basic criteria for accepting new core modules

2001-04-22 Thread David Grove
Michael G Schwern <[EMAIL PROTECTED]> wrote: > Sorry, it wasn't clear to the perl-qa folks that I'm talking about > Perl5, not Perl6. > > No nonononono. Please don't drag CPAN into this particular > conversation. I'm just trying to nail down p5p on this simple issue. > > Sorry for not c

Re: Proposed basic criteria for accepting new core modules

2001-04-22 Thread Michael G Schwern
Sorry, it wasn't clear to the perl-qa folks that I'm talking about Perl5, not Perl6. On Sun, Apr 22, 2001 at 10:43:12PM +, David Grove wrote: > I do, however, think that it would be a good absolute to have a > requirement of standard internal documentation, not just for the > core, but to CP

Re: Proposed basic criteria for accepting new core modules

2001-04-22 Thread David Grove
Michael G Schwern <[EMAIL PROTECTED]> wrote: > I'd like to propose two simple critereon for all future module > additions to the core: > > 1) It has a reasonable amount of POD documentation. At minimum it > must have something, even if its just a NAME, SYNOPSIS and > DESCRIPTION. This is

Re: Proposed basic criteria for accepting new core modules

2001-04-22 Thread Michael G Schwern
On Sun, Apr 22, 2001 at 11:52:12AM +0200, Johan Vromans wrote: > Personally, I'd like to impose these to any CPAN submission > whatsoever... Let's not dig into that 55-gallon drum of man-eating nightcrawlers here, K? As for below, I'd do this as a two-stage process. First, let's all agree that

Re: Untested libraries.

2001-04-22 Thread Nicholas Clark
On Sun, Apr 22, 2001 at 01:54:31AM +0100, Michael G Schwern wrote: > On Sat, Apr 21, 2001 at 07:21:47PM -0500, Jarkko Hietaniemi wrote: > > > Net::Ping > > > > Maybe hard to test anything meaningful portably. > > localhost is always an option, no? If nothing else we can make sure > an object c

Re: Untested libraries.

2001-04-22 Thread Jarkko Hietaniemi
On Sun, Apr 22, 2001 at 01:54:31AM +0100, Michael G Schwern wrote: > At minimum, everything should at least have a "do I compile and export > the documented interface" test. > > Curmudgeon's anti-excuses follow. Pumpkin's anti-anti-excuses follow. > > > CGI::Carp > > > CGI::Cookie > > > CGI::Pu

Re: Untested libraries.

2001-04-22 Thread Jarkko Hietaniemi
> System dependent. Similar issues as with User:: > > > PerlIO > > Err, nothing much would work in bleadperl if PerlIO didn't since > it's the "stdio" layer... PerlIO::Scalar and PerlIO::Via could use tests, though. -- $jhi++; # http://www.iki.fi/jhi/ # There is this special biologis

Re: Untested libraries.

2001-04-22 Thread Michael G Schwern
At minimum, everything should at least have a "do I compile and export the documented interface" test. Curmudgeon's anti-excuses follow. On Sat, Apr 21, 2001 at 07:21:47PM -0500, Jarkko Hietaniemi wrote: > > CPAN (since I know the CPAN version has tests) > > Yes, rather network

Re: Untested libraries.

2001-04-22 Thread Russ Allbery
Jarkko Hietaniemi <[EMAIL PROTECTED]> writes: > On Sat, Apr 21, 2001 at 10:32:35PM +0100, Michael G Schwern wrote: >> filetest > System dependent, requires filesystems with ACLs. Even if we had tests that would just be skipped if Perl wasn't being built under a path starting with /afs, there ar

Re: Proposed basic criteria for accepting new core modules

2001-04-22 Thread Johan Vromans
Michael G Schwern <[EMAIL PROTECTED]> writes: > I'd like to propose two simple critereon for all future module > additions to the core: > [two simple critereon follow] Personally, I'd like to impose these to any CPAN submission whatsoever... For modules to be part of the core the requirements c

Re: Untested libraries.

2001-04-22 Thread Jarkko Hietaniemi
On Sat, Apr 21, 2001 at 10:32:35PM +0100, Michael G Schwern wrote: > After patching up 1_compile.t, I now have a fairly accurate list of > all the modules which are never even mentioned in the tests. They are > listed below. Its a little over a third of the whole distribution > (I'm not counting