This is what is happening:
- Perl forks itself. The main program then wait()'s
for the child to finish.
- The child gets a copy of everything that is in the
parents environment (actually, it shares the memory using
copy-on-write, but thats more detail than we need right now).
- When the child goes away, everything that was in the
child's copy is destroyed.
- When the parent resumes operation, it has the same
environment as before it forked since nothing ever actually
changed it's copy.
If you need to have a second process alter the memory
or environment of another process, you need to look into
programming with threads or shared memory. Your other
alternative would be inter-process communication.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
