<?xml version="1.0" encoding="windows-1252"?>
<node id="428906" title="Re^3: brian's Guide to Solving Any Perl Problem (@EXPORT_OK++)" created="2005-02-07 23:11:51" updated="2005-08-10 14:45:52">
<type id="11">
note</type>
<author id="22609">
tye</author>
<data>
<field name="doctext">
&lt;blockquote&gt;&lt;i&gt;
Most style guides I work under ask for the full package name of external functions
&lt;/i&gt;&lt;/blockquote&gt;&lt;p&gt;
What an awful idea.  Just being explicit about what you import from any module you [use] is a much better idea.  @EXPORT is evil but @EXPORT_OK makes for easier-to-read/-write code and provides reasonable interface verification (at compile time, no less).  [demerphq] already said all of this, but I just boggle at the sentence I quoted so I had to chime in against such insanity.
&lt;/p&gt;
&lt;div class="pmsig"&gt;&lt;div class="pmsig-22609"&gt;&lt;p align="right"&gt;
- [tye]&lt;tt&gt; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;&lt;/tt&gt;
&lt;/p&gt;&lt;/div&gt;&lt;/div&gt;</field>
<field name="root_node">
376075</field>
<field name="parent_node">
376599</field>
</data>
</node>
