t/sample-tests/switches

[Andy Armstrong]

t/sample-tests/switches expects strict.pm not to have been included.  
That assumption breaks if, for example, a smoke harness is using  
PERL5OPT to load a module that includes strict.pm.

For example:

PERL5OPT="-Mstrict" prove -b t/compat/test-harness-compat.t

This has been broken for a while - I just checked as far back as 3.07  
but it's probably been broken since the initial 3.00 release. It's  
just come to light because CPAN::Reporter now used PERL5OPT - which  
it's perfectly entitled to do.

Ovid originally wrote t/sample-tests/switches and the tests that use  
it. I'm not sure what the intention of the test is or whether it's  
still valuable. It seems that the condition it tests isn't something  
we can rely on.

Should it be removed? Expressed differently? I'm leaning towards  
deleting it.

Patient: It hurts when I check $INC{'strict.pm'}
Doctor: Don't do it then.

-- 
Andy Armstrong, Hexten