On 2011.11.10 7:44 PM, chromatic wrote:
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.
That argument happened well after Test::Harness was written to set -w. If nothing else, it's a major compatibility issue.
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.)
We're discussing how to deal with the reality and smooth over the existing differences between the various ways to run a test.
If you want to crack open the -w in testing discussion, start another thread and lay out your argument.
-- Whip me, beat me, make my code compatible with VMS!
