ANNOUNCE Test::Inline 0.11

2001-08-30 Thread Michael G Schwern
Ooops, just realized I released that one without a date in the Changes file. Oh well. Just a couple of minor things. The most important one being that pod2test will no longer produce any output if there's no embedded tests. http://www.pobox.com/~schwern/src/Test-Inline-0.11.tar.gz 0.11 Thu

Re: ANNOUNCE: Pod::Coverage 0.02 release

2001-08-30 Thread Richard Clamp
On Thu, Aug 30, 2001 at 07:07:42PM +0200, Tels wrote: > Attached is a script to test all modules in a dist, Attachment error #1 > I think a "make > pod-cover" and "make test-cover" would be cool, but I am not able to do such > a beast. Me also

Re: What in t/op can use Test::More and what can't.

2001-08-30 Thread Michael G Schwern
On Thu, Aug 30, 2001 at 05:17:57PM -0400, Joe McMahon wrote: > Am I being goofy if I want to fix the stuff that I know is bad even if > it can't be done via an ok() function? I seem to recall that the > print "not " unless something; > print "ok xx\n"; > > occurs a lot and make VMS all urpy.

[PATCH pod/perlhack.pod] Yet another improvement to the patching example

2001-08-30 Thread Michael G Schwern
This gives a simpler implementation of ok() that also includes descriptive names. --- pod/perlhack.pod2001/08/28 13:54:34 1.1 +++ pod/perlhack.pod2001/08/30 21:00:31 @@ -1481,13 +1481,12 @@ my $test = 1; sub ok { -my($ok) = @_; +my($ok, $name) = @_;

Re: What in t/op can use Test::More and what can't.

2001-08-30 Thread Michael G Schwern
On Thu, Aug 30, 2001 at 09:25:23PM +0200, H.Merijn Brand wrote: > If I'm right, this is the format test, ain't it? If so, be > *extremely* careful with the last part (60 lines or so), cause it > depends on the way the IO handles are dealt with (nested write's) Hmmm... you're messing with STDOUT.

Re: What in t/op can use Test::More and what can't.

2001-08-30 Thread H.Merijn Brand
On Thu 30 Aug 2001 20:46, Michael G Schwern <[EMAIL PROTECTED]> wrote: > Ok, quick run-through of what in t/op it's safe to use Test::More > with. 'Yes' means use Test::More. 'No' means use an 'ok' function. > 'No way' means you can't even use an 'ok' function. > > This is just a quick, cursory

Re: More diffs (right format this time)

2001-08-30 Thread Michael G Schwern
On Thu, Aug 30, 2001 at 02:18:31PM -0400, Joe McMahon wrote: > >Hmmm. concat.t is wy too basic to use Test::More on it. delete.t > >is pushing it. die.t and die_exit.t cannot be tested with Test::More > >since it relies on that functionality. > > > Okay, not a problem. I can clean up the pr

What in t/op can use Test::More and what can't.

2001-08-30 Thread Michael G Schwern
Ok, quick run-through of what in t/op it's safe to use Test::More with. 'Yes' means use Test::More. 'No' means use an 'ok' function. 'No way' means you can't even use an 'ok' function. This is just a quick, cursory overview. Scream if something looks wrong. t/op/64bitint.t Yes t/op/an

Re: More diffs (right format this time)

2001-08-30 Thread Michael G Schwern
On Thu, Aug 30, 2001 at 01:05:35PM -0400, Joe McMahon wrote: > I've switched over to using is() for anything that wasn't an '==' > test' on funky numeric values; there are a lot of those in (e.g.) > bop.t, and I didn't want to change the fundamental nature of the > tests. I've also gotten my diff