perlipc for AS 5.8 says:
CAVEATS AND LIMITATIONS
BEGIN blocks
The fork() emulation will not work entirely correctly when called from within a BEGIN block. The forked copy will run the contents of the BEGIN block, but will not continue parsing the source stream after the BEGIN block.
Which may or may not be relevant to IPC::open3 (which must do an emulated fork under the covers), but as I just re-read this a few minutes ago, I thought it worth mentioning. You might be better off using an INIT block rather than a BEGIN block.
In reply to Re: Windows & IPC -- request for comments
by BrowserUk
in thread Windows & IPC -- request for comments
by rkg
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |