<?xml version="1.0" encoding="windows-1252"?>
<node id="431855" title="Re: José's Guide for creating Perl modules" created="2005-02-17 02:38:02" updated="2005-08-13 14:43:15">
<type id="11">
note</type>
<author id="176576">
eyepopslikeamosquito</author>
<data>
<field name="doctext">
&lt;P&gt;
Very nice. This tutorial covers some of the things I plan on covering when I finally get around to writing a tutorial
based on [id://418891]. Update: I just noticed [id://158999] and [id://102347] both of which look excellent.
&lt;/P&gt;

&lt;P&gt;
In addition to strict and warnings, don't forget
taint mode testing.
Re coding style, Abigail's [id://215675] is worth a read.
&lt;/P&gt;

&lt;P&gt;
It's vital to choose a good interface first time. Once your module is released into the wild it may become practically impossible to change its interface; anything else can be fixed later. Two good nodes I've noticed re creating good interfaces are [id://338941] and [id://317520]. Any other good ones, please let me know. &lt;B&gt;Update:&lt;/B&gt; I couldn't find any more, so I wrote one: [id://553487].
&lt;/P&gt;

&lt;P&gt;
&lt;B&gt;Update:&lt;/B&gt; I expect [TheDamian]'s upcoming book "Perl Best Practices" will have some sound advice on this subject.
&lt;/P&gt;
</field>
<field name="root_node">
431702</field>
<field name="parent_node">
431702</field>
</data>
</node>
