Hello wise monks. Many thanks for helping me identify the source of the problem that is the cmd.exe QuickEdit mode last time.

But now I need your wisdom again.

Suppose we have two perl files, parent.pl and child.pl. We start by running parent.pl, which will start another process to run child.pl. How do I propagate the errors in child.pl to parent.pl.

This is parent.pl

#!/usr/bin/perl
use Win32::Process;

for (1..3) {
  eval {
    print "$_\n";
    Win32::Process::Create(my $proc, $^X, "perl child.pl", 0, 0, ".");
  };
  if ($@) {
    if (index($@, 'Custom Exception') == 0) {
      print "Caught exception: $@";
      next;
    } else {
      die $@;
    }
  }
}
[download]

And this is child.pl

#!/usr/bin/perl
die 'Custom Exception';
[download]

As you can see, what I'm trying to do is to iterate to the next loop (instead of simply die-ing) when a custom exception is caught. This works if the code inside the eval block is still in same process. However, eval does not seem to be able to catch errors that are in another process. I have tried some modules like Error and Error::TryCatch as well but nothing works.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.