| … | |
… | |
| 591 | |
591 | |
| 592 | If you want to execute some code (that isn't in a module) to take over the |
592 | If you want to execute some code (that isn't in a module) to take over the |
| 593 | process, you should compile a function via C<eval> first, and then call |
593 | process, you should compile a function via C<eval> first, and then call |
| 594 | it via C<run>. This also gives you access to any arguments passed via the |
594 | it via C<run>. This also gives you access to any arguments passed via the |
| 595 | C<send_xxx> methods, such as file handles. See the L<use AnyEvent::Fork as |
595 | C<send_xxx> methods, such as file handles. See the L<use AnyEvent::Fork as |
| 596 | a faster fork+exec> example. |
596 | a faster fork+exec> example to see it in action. |
| 597 | |
597 | |
| 598 | Returns the process object for easy chaining of method calls. |
598 | Returns the process object for easy chaining of method calls. |
| 599 | |
599 | |
| 600 | =cut |
600 | =cut |
| 601 | |
601 | |
