Mmm. Asynchronous is perhaps not 100% correct but it's not as simple as do one thing, then do something else. I want to fire the main code at one point (filterd), do something(fire filtqmail), and then check the main program's output. I can't fire the code and capture its output and THEN prod it into motion, which at least from an initial read is what it looks like Capture::Tiny does. While it's interesting and probably a useful thing for me to know about in the future I'm not sure that it accomplishes what I need it to. So far the best answer has been a file handle to the output so I can check it when I want to.
That said the link on Dave Golden's talk was awesome. Thanks for that.
| [reply] |