Short answer: You cannot with Proc::Simple (longer: in your case when starting a
sub{...} as a child process)
This is what happens in the child part of the fork() that is executed for your $func = sub{...};
# in Proc::Simple
# $func = sub{ ... }; # your code
...
if(ref($func) eq "CODE") {
$self->dprt("Launching code");
$func->(@params); exit 0; # Start perl subroutine
} else {
...
So, the exit 0 (successful execution) is all that is returned from your sub{...}.
The $return value is discarded.
Your sub{...} could return the result to the main process by means of IPC or
by storing the result in a temporary file
(e.g. YAML, JSON, Storable, etc.). The parent process could read
the result from a pipe or load the serialised data from a file after the sub has finished.
Update: IPC::Lite
However, I guess, that in this particular case, you're better off with threads
and maybe a queue.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Outside of code tags, you may need to use entities for some characters:
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
|
|
