Re^2: Why Does Test::Deep Kill Test::Class

in reply to Re: Why Does Test::Deep Kill Test::Class
in thread Why Does Test::Deep Kill Test::Class

Sheesh. I was checking RT bugs and Changelogs, but somehow didn't think about Google :)

Updating Test::Deep solved this. Thanks. (Whew!)

What a painfully long day this is.

Cheers,
Ovid

New address of my CGI Course.

Comment on Re^2: Why Does Test::Deep Kill Test::Class

Replies are listed 'Best First'.
Re^3: Why Does Test::Deep Kill Test::Class by fergal (Chaplain) on Jun 20, 2008 at 14:46 UTC
This and some other stuff are the root of my hatred of default exports (and the lack of a nice way to use things without exports at all).	[reply]
Re^4: Why Does Test::Deep Kill Test::Class by Your Mother (Archbishop) on Jan 09, 2009 at 19:59 UTC
A bit late reply, sorry, but I find "()" to be quite nice. You just have to cultivate the habit of using it.	[reply]
Re^5: Why Does Test::Deep Kill Test::Class by fergal (Chaplain) on Mar 20, 2009 at 16:45 UTC
`()` would be fine if you didn't then have to type `use Foo::Bar::Woz::Snuts (); Foo::Bar::Woz::Snuts::Wibble($x, $y)` [download] Python gets it right (well better at least) with `from foo.bar.woz import snuts; snuts.wibble(x, y)` [download] and suchlike. This is pretty much impossible in Perl due to symbol table access being absolute, not relative.	[reply] [d/l] [select]
Re^6: Why Does Test::Deep Kill Test::Class by Your Mother (Archbishop) on Mar 20, 2009 at 18:01 UTC
Re^7: Why Does Test::Deep Kill Test::Class by fergal (Chaplain) on Mar 26, 2009 at 13:06 UTC

In Section Seekers of Perl Wisdom