In general, processes don't share memory. There are methods which may pull it off, but I prefer to stick to "threads share, processes keep private."

At fork time, the child owns its own copy of the stuff in memory. Let it work on whatever it likes. The child should serialize (save) a copy of an object to be handed back to the parent if necessary. The parent then discovers these saved object (filename, socket connect, etc.) and deserializes (loads) the copy into its own memory space.

There are a number of approaches to serialization. I suggest using Data::Dumper/eval until you're familiar with the process, then look for more efficient storage methods later.

--
[ e d @ h a l l e y . c c ]

In reply to Re: Sharing objects between processes by halley
in thread Sharing objects between processes by Marcello

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • 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, details, 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, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.