| … | |
… | |
| 371 | |
371 | |
| 372 | There is an important twist - the C<AnyEvent::Fork::RPC::event> function |
372 | There is an important twist - the C<AnyEvent::Fork::RPC::event> function |
| 373 | is only defined when the child is fully initialised. If you redirect the |
373 | is only defined when the child is fully initialised. If you redirect the |
| 374 | log messages in your C<init> function for example, then the C<event> |
374 | log messages in your C<init> function for example, then the C<event> |
| 375 | function might not yet be available. This is why the log callback checks |
375 | function might not yet be available. This is why the log callback checks |
| 376 | whether the fucntion is there using C<defined>, and only then uses it to |
376 | whether the function is there using C<defined>, and only then uses it to |
| 377 | log the message. |
377 | log the message. |
| 378 | |
378 | |
| 379 | =head1 PARENT PROCESS USAGE |
379 | =head1 PARENT PROCESS USAGE |
| 380 | |
380 | |
| 381 | This module exports nothing, and only implements a single function: |
381 | This module exports nothing, and only implements a single function: |
