Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • by dagolden (6584) on 2007.12.31 19:57 (#59873) Journal
    It says pretty clearly that it creates a directory in tmpdir -- and references File::Spec. And File::Spec clearly cites tainting. What's so surprising?

    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 where a test file uses taint mode and calls something that eventually invokes a fork -- which causes a segfault on 5.8.8. (E.g. try "perl -Te fork" on 5.8.8 to see it. It seems to be fixed on 5.10.0 thankfully.) I just think that taint mode in tests files is a bad idea unless one really needs it.

    -- dagolden
    • Well, RTFM is a funny thing...the farther away from the module you're using, the less he lack RTFMing is the users fault. As a user of Directory::Scratch, should I have to RTFM three to four levels deep to find one mention of tempdir producing two different results when in and out of taint mode?

      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,