<?xml version="1.0" encoding="windows-1252"?>
<node id="929259" title="Re^10: Win32, fork and XS globals" created="2011-10-02 23:34:45" updated="2011-10-02 23:34:45">
<type id="11">
note</type>
<author id="381608">
ikegami</author>
<data>
<field name="doctext">
&lt;blockquote&gt;&lt;p&gt;&lt;i&gt;In C, the keyword 'static' has a very particular meaning and purpose. It denotes both persistence and limited visiblity. &lt;/i&gt;&lt;/blockquote&gt;

&lt;p&gt;Yes, and the mechanism provides the same persistence and limited visibility in Perl's memory space.

&lt;blockquote&gt;&lt;p&gt;&lt;i&gt;But the main problem is that what the macros actually do is not explained. &lt;/i&gt;&lt;/blockquote&gt;

&lt;p&gt;Which one do you think isn't explained? Unless I'm missing one, the example explains exactly how to use each one.

&lt;blockquote&gt;&lt;p&gt;&lt;i&gt;You try to come across all superior, by taking the documentation as gospel and good, and quoting it verbatim, rather than actually thinking through the implications.&lt;/i&gt;&lt;/blockquote&gt;

&lt;p&gt;Your argument is lost because every premise is completely wrong.

&lt;ul&gt;
&lt;li&gt;I didn't take the docs as gospel. I've actually used the mechanism recently. It was easy, it did the trick, and it should do the trick for the OP.
&lt;li&gt;I didn't quote any docs.
&lt;li&gt;I did think through the implications: It solves the OP's problem cleanly and simply. Perhaps you are over-thinking it or trying to make a political statement.
&lt;/ul&gt;

&lt;blockquote&gt;&lt;p&gt;&lt;i&gt;Instead of just trying to help the OP, you try to make political capital from a documentation reference. &lt;/i&gt;&lt;/blockquote&gt;

&lt;p&gt;That makes no sense. I simply provided a link that explained how to use the mechanism *you* suggested, since you completely failed to help the OP in that regard.
</field>
<field name="root_node">
929097</field>
<field name="parent_node">
929205</field>
</data>
</node>
