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
-BEGIN PGP SIGNED MESSAGE-
Moin,
On Sunday 26 June 2005 07:18, Collin Winter wrote:
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
On Sun, Jun 26, 2005 at 10:25:51AM +0200, Tels wrote:
After tinkering with B::Deparse for a bit, I think this particular
oddity may just be a result of poorly-written docs (or, more
probably, poorly-read on my part). The module seems to do the right
thing in all cases I could come up with
Tels wrote :
-BEGIN PGP SIGNED MESSAGE-
Moin,
On Sunday 26 June 2005 07:18, Collin Winter wrote:
[...]
After tinkering with B::Deparse for a bit, I think this particular
oddity may just be a result of poorly-written docs (or, more
probably, poorly-read on my part). The module seems
On Sun, Jun 26, 2005 at 12:06:47PM +0200, David Landgren wrote:
What it *shouldn't* do is what Test.pm does, namely execute the
code ref and compare the values returned. It would just compare
the refernces.
Why should it not do that? Is this because of subs with side effects?
Isn't
You have 3 situations
1 the refs came from \somefunc
2 the refs come from evaling strings of code
3 the refs are closures and therefore have some data associated with them
For 3, it looks like B::Deparse does't handle the data at all so even
if the deparsed subs are identical they may behave
David Landgren writes:
Michael Schwern wrote at the beginning of this thread:
What it *shouldn't* do is what Test.pm does, namely execute the
code ref and compare the values returned. It would just compare
the refernces.
Why should it not do that? Is this because of subs with side
On 6/26/05, Fergal Daly [EMAIL PROTECTED] wrote:
You have 3 situations
1 the refs came from \somefunc
2 the refs come from evaling strings of code
3 the refs are closures and therefore have some data associated with them
For 3, it looks like B::Deparse does't handle the data at all so
On Sun, Jun 26, 2005 at 12:57:05PM +0100, Fergal Daly wrote:
1 the refs came from \somefunc
2 the refs come from evaling strings of code
3 the refs are closures and therefore have some data associated with them
For 3, it looks like B::Deparse does't handle the data at all so even
if the
