<?xml version="1.0" encoding="windows-1252"?>
<node id="309000" title="Re: Re: A (memory) poor man's hash" created="2003-11-21 13:43:57" updated="2005-06-15 18:41:42">
<type id="11">
note</type>
<author id="195718">
hardburn</author>
<data>
<field name="doctext">
&lt;p&gt;&lt;em&gt;I still find hashes a little daunting.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;[BrowserUK] (if I may presume) was speaking in relative terms. Hashes are quite easy compared to (for example) Perl's advanced data structures, object system, or closures.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;While hashes may have a tendancy to soak up a lot of memory, it's not using it for that long.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;The problem is that perl usually doesn't free the memory back to the OS until the process exits (though it will reuse that memory for other things). This is particularly a problem for mod_perl, where the process will stick around as long as Apache is up (potentially years, if your sysadmin is neglegent about security patches ;).&lt;/p&gt;

&lt;div class="pmsig"&gt;&lt;div class="pmsig-195718"&gt;
&lt;p&gt;----&lt;br&gt;&lt;em&gt;I wanted to explore how Perl's closures can be manipulated, and ended up creating an object system by accident.&lt;/em&gt; &lt;br&gt;
-- [Schemer]&lt;/p&gt;

&lt;p&gt;&lt;code&gt;: () { :|:&amp; };:&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;Note&lt;/b&gt;: All code is untested, unless otherwise stated&lt;/p&gt;

&lt;/div&gt;&lt;/div&gt;</field>
<field name="root_node">
308947</field>
<field name="parent_node">
308993</field>
</data>
</node>
