Re: Push it real good, or don't

Data saved in a child process is not visible in the parent. (Although using threads that works.)

Update: To clarify, a forked child inherits existing data from the parent process (i.e. the $pm object.) On the other hand, when a child dies, the parent receives nothing other than a notice if the parent is looking for it. (Although it can be argued that a parent can inherit insanity from a child.)

You must always remember that the primary goal is to drain the swamp even when you are hip-deep in alligators.

Comment on Re: Push it real good, or don't Download Code

Replies are listed 'Best First'.
Re^2: Push it real good, or don't by pimperator (Acolyte) on Jun 09, 2014 at 20:16 UTC
Ahhh I think this is the issue at hand. How do I solve it?	[reply]
Re^3: Push it real good, or don't by Laurent_R (Canon) on Jun 09, 2014 at 20:56 UTC
Not necessarily the best answer, but one way to do it is for the child to write to a file and the parent to read it. But that is just an idea on how to do it, I am far from being an expert on these things.	[reply]
Re^3: Push it real good, or don't by boftx (Deacon) on Jun 09, 2014 at 20:21 UTC
Well, the first question is this: Do you really need to run this as a forked process? You must always remember that the primary goal is to *drain the swamp* even when you are hip-deep in alligators.	[reply]
Re^4: Push it real good, or don't by pimperator (Acolyte) on Jun 09, 2014 at 20:38 UTC
Yes this is a test for a much larger script	[reply]
Re^5: Push it real good, or don't by boftx (Deacon) on Jun 09, 2014 at 20:51 UTC
Re^5: Push it real good, or don't (RTfM?) by LanX (Saint) on Jun 09, 2014 at 20:53 UTC