[ANNOUNCE] Module::Info 0.09 little bug fix

2001-12-10 Thread Michael G Schwern
http://www.pobox.com/~schwern/src/Module-Info-0.09.tar.gz Had a little bug where 'require 5.004' would cause trouble. -- Michael G. Schwern <[EMAIL PROTECTED]>http://www.pobox.com/~schwern/ Perl Quality Assurance <[EMAIL PROTECTED]> Kwalitee Is Job One We have returned to cl

[ANNOUNCE] Module::Info 0.08 now with modules_used()!

2001-12-10 Thread Michael G Schwern
This is the Egg Shen release [1] of Module::Info. http://www.pobox.com/~schwern/src/Module-Info-0.08.tar.gz This release adds modules_used(). Tells you all the modules and files required or used by the module in question using the backend compiler. As such its more reliable than a regex-based on

[ANNOUNCE] Module::Info 0.07

2001-12-10 Thread Michael G Schwern
http://www.pobox.com/~schwern/src/Module-Info-0.07.tar.gz New version of Module::Info. I figured out how to implement subroutines(). This uses the backend compiler and isn't subject to the caveats of a regex based one. If there's a subroutine defined when the module loads, it'll find it. In o

Why ok() isn't enough (was Re: is() with arbitrary comparisions)

2001-12-10 Thread Michael G Schwern
On Mon, Dec 10, 2001 at 06:53:20PM -0800, Kurt D. Starsinic wrote: > Why go to such trouble to have 20 different automagical comparators, > when you can do whatever you want with anonymous subs and/or eval in ok()? > Where's the real value? Frankly, I'm getting pretty confused by the > myriad

Re: is() with arbitrary comparisions

2001-12-10 Thread Kurt D. Starsinic
On Dec 10, Michael Schwern wrote: > I think I have a solution to the rigidity of is(). ie. something with > the diagnostic output of is(), but the flexibility of ok(). > > The principle idea being to replace code like: > > ok( $foo <= $bar ) || print "# $foo <= $bar\n"; > > Provide an is()

Re: Test::More::diag()

2001-12-10 Thread Michael G Schwern
On Mon, Dec 10, 2001 at 11:19:21PM +, Adrian Howard wrote: > > I'm planning on using diag(). > > > > ok( $foo == $bar ) || diag 'blah blah'; > > > > it has nice mnemonics with: > > > > open(FOO, "bar") || die 'blah blah'; > > > > "ok or diag" "open or die" > > > > Thoughts? > > Little to

Re: Test::More::diag()

2001-12-10 Thread Adrian Howard
Hi, Newbie with Test::More --- and loving it :-) on 10/12/01 12:04 pm, Michael G Schwern at [EMAIL PROTECTED] wrote: > Its been on the Test::More todo list to have a blessed way to do: > > print STDOUT "# here's some extra info\n"; > > I'm planning on using diag(). > > ok( $foo == $bar ) ||

Test::More::diag()

2001-12-10 Thread Michael G Schwern
Its been on the Test::More todo list to have a blessed way to do: print STDOUT "# here's some extra info\n"; I'm planning on using diag(). ok( $foo == $bar ) || diag 'blah blah'; it has nice mnemonics with: open(FOO, "bar") || die 'blah blah'; "ok or diag" "open or die" Thoughts

is() with arbitrary comparisions

2001-12-10 Thread Michael G Schwern
I think I have a solution to the rigidity of is(). ie. something with the diagnostic output of is(), but the flexibility of ok(). The principle idea being to replace code like: ok( $foo <= $bar ) || print "# $foo <= $bar\n"; Provide an is() variant that takes an arbitrary op! My working t

Re: Real Low Fruit

2001-12-10 Thread Tim Jenness
On Mon, 10 Dec 2001, Richard Clamp wrote: > The UntestedModules portion of the Wiki misidentifies Pod::LaTeX and > Pod::ParseUtils as having no tests, so we get those for free. > The tests test the "old" parsing of links not the new versions defined in perlpodspec. I think Pod::ParseUtils will

Real Low Fruit

2001-12-10 Thread Richard Clamp
The UntestedModules portion of the Wiki misidentifies Pod::LaTeX and Pod::ParseUtils as having no tests, so we get those for free. Of course I managed not to spot this till after I'd lightly patched the CPAN test for Pod::LaTeX into happiness, and was about to frob the MANIFEST. Undercaffinated.