in reply to Re^2: forked die() in eval block has counterintuitive behavior?
in thread forked die() in eval block has counterintuitive behavior?

An unexpected child die() gets caught by a containing eval block that thinks it's just dealing with the parent.

I don't think this problem is specific to eval{}. Any code which is going to fork needs to be careful about which code is going to run in the parent and which in the child. It's just a fact of Unix programming, not really a problem with Perl specifically.

-sam

  • Comment on Re^3: forked die() in eval block has counterintuitive behavior?

In Section Seekers of Perl Wisdom