<?xml version="1.0" encoding="windows-1252"?>
<node id="195894" title="Re: How to morph a plain module to OO" created="2002-09-07 15:10:41" updated="2005-08-13 15:13:03">
<type id="11">
note</type>
<author id="182681">
sauoq</author>
<data>
<field name="doctext">
&lt;p&gt;My first suggestion is not to do this. If you have a working module and it is already heavily used, just write a new module for the OO stuff and have &lt;em&gt;it&lt;/em&gt; use the old module under the covers. It is far too easy to break the original code in subtle ways.&lt;/p&gt;

&lt;p&gt;As an illustration, you already broke the functionality of your original module because your new isFile() doesn't take a verbose argument when it isn't used as a method.&lt;/p&gt;





&lt;pre&gt;
-sauoq
"My two cents aren't worth a dime.";
&lt;/pre&gt;</field>
<field name="root_node">
195887</field>
<field name="parent_node">
195887</field>
</data>
</node>
