Fwd: [CPAN Upload: P/PE/PETDANCE/Test-Harness-2.51_02.tar.gz: upload@pause.perl.org]

2005-06-25 Thread Andy Lester
I've just uploaded Test::Harness 2.51_02. It turns off the timer by default, and adds a --timer switch to prove. Please try it out and see if all is well because I'm going to make it 2.52 tomorrow. And now, I must go to bed so I can drive to Toronto... xoxo, Andy -- Andy Lester => [EMAIL PROT

Re: is_deeply() and code refs

2005-06-25 Thread Collin Winter
> > My initial quick-glance at B::Deparse's documentation mentions > > something about perl optimising certain constants away, which could > > well throw a spanner into the works. Storable uses B::Deparse when > > serialising coderefs, though, so I'm certain there's a way around > > this. > > That

Re: is_deeply() and code refs

2005-06-25 Thread Michael G Schwern
On Sun, Jun 26, 2005 at 12:08:35AM -0400, Collin Winter wrote: > My inital strategy for implementing this was a two-tiered approach. > First, compare the references; if they're the same, return true, go no > futher. If they differ, however, say if anonymous subs were thrown > into the mix, then use

Re: is_deeply() and code refs

2005-06-25 Thread Collin Winter
I'll chime in, as I'm the one who initially raised the idea : ) I'll start with a use-case: my initial motivation for having is_deeply handle coderefs came up while building certain unit tests for a rewrite of DBD::Mock. Several of the worker functions return complex data structures -- which may c

is_deeply() and code refs

2005-06-25 Thread Michael G Schwern
Currently, throwing is_deeply() a code ref causes it to barf. perl -MTest::More -wle 'print is_deeply sub {}, sub {}' WHOA! No type in _deep_check This should never happen! Please contact the author immediately! # Looks like your test died before it could output anything. is_deeply() doesn't k