I'm posting this so maybe someone else will learn from my pain. I just spent an hour trying to figure out why Directory::Scratch and File::Temp were creating temp directorys in $ENV{TMP} on one test script under Win32, and in the cwd() on another script.
Of course, the answer is that one test has -T, and one does not. With tainting on of course, there is no ENV (TMP/TEMP), so the cwd() is used. It makes sense, but in a way feels like a bug.
At the very least, maybe that should be a big fat warning on the File::Temp pod.
doc patches welcome (Score:2)
DWIM or RTFM? (Score:1)
I think you need to ask yourself why you're running tests in taint mode. Are you testing something that specifically involves taint mode? If so, great. If not -- and you're doing it "just because", then you're setting yourself up to be surprised when the computer goes ahead and does exactly what you asked it to do.
I used to see this a lot on Windows wher
Re: (Score:1)
As far as running tests under taint mode, I do it for one reason only: to sooner find our what doesn't work under taint mode. There is nothing more frustrating than trying to turn on Taint in Apache/ModPerl instance,