<?xml version="1.0" encoding="windows-1252"?>
<node id="216726" title="Re: My coding guidelines" created="2002-12-01 00:05:41" updated="2005-03-23 18:17:58">
<type id="11">
note</type>
<author id="182681">
sauoq</author>
<data>
<field name="doctext">
&lt;p&gt;Excellent. ++[Abigail-II|Abigail] once for the whole thing and once each for 30, 31, and 32.&lt;/p&gt; 
&lt;p&gt;Of course, I don't follow all of those guidelines but most of the ones I don't are cosmetic.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;I don't use whitespace between indices.&lt;/li&gt;
&lt;li&gt;I cuddle my elses.&lt;/li&gt;
&lt;li&gt;I don't use whitespace around the &lt;code&gt;-&gt;&lt;/code&gt;, &lt;code&gt;++&lt;/code&gt; and &lt;code&gt;--&lt;/code&gt; operators.&lt;/li&gt;
&lt;li&gt;I prefer either &lt;code&gt;foo($bar)&lt;/code&gt; or &lt;code&gt;foo( $bar )&lt;/code&gt; to &lt;code&gt;foo ($bar)&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;I use Getopt::Std and eschew long options. I do provide -h and -V for usage and version banners though.&lt;/li&gt;
&lt;/ul&gt;

&lt;blockquote&gt;&lt;em&gt;This is just a first draft. I've probably forgotten some rules.&lt;/em&gt;&lt;/blockquote&gt;

&lt;p&gt;How about your guidelines for breaking long lines?&lt;/p&gt;

&lt;pre&gt;
-sauoq
"My two cents aren't worth a dime.";
&lt;/pre&gt;</field>
<field name="root_node">
215675</field>
<field name="parent_node">
215675</field>
</data>
</node>
