in reply to Re^2: File::Temp randomness when forking
in thread File::Temp randomness when forking

That's not necessarily what I meant. If you'd have cut down your code to the essentials you would have removed the tempdir call before the loop and suddenly it would not have failed. You'd then at least have this extra bit of information which you could have checked up on yourself in the File::Temp code or added to the post. And it would have been easier for someone to look at the problem and figure out what the problem was without the irrelevant bits of information. As I said, just an aside for future reference, sorry if it maybe came across a little harsh.


Debugging is twice as hard as writing the code in the first place. Therefore, if you write the code as cleverly as possible, you are, by definition, not smart enough to debug it. -- Brian W. Kernighan
  • Comment on Re^3: File::Temp randomness when forking

Replies are listed 'Best First'.
Re^4: File::Temp randomness when forking
by ryantate (Friar) on Nov 29, 2005 at 18:07 UTC
    If you'd have cut down your code to the essentials you would have removed the tempdir call before the loop and suddenly it would not have failed.

    I see your broader point. I updated the node (before your reply) with the following sentence, I should have used an UPDATE tag but was hoping I was fast enough:

    "On further consideration, I would probably cut it down as you suggest, and deal with any 'why did you do this questions as they come up (instead of preempting them).

    That'll teach me to try and outrun other monks ;->

    UPDATE: In reality, I might not have rid myself of tempdir, the cut-down version you posted had it in there after all! But I do see your point.