On Thursday, November 10, 2011 at 05:57 PM, Michael G wrote:
> If you don't want global warnings, explicitly turn them off with BEGIN { $^W
=
> 0 }.
I thought the argument that test modules should set global policy unilaterally
died out when I made Test::MockObject *not* enable UNIVERSAL::isa and
UNIVERSAL::can by default.
It's the 21st century. Why can't Test::Harness find a nice middle ground and
respect the lexical encapsulation of warnings introduced in 2000? (I think it
just might catch on.)
-- c