<?xml version="1.0" encoding="windows-1252"?>
<node id="952597" title="Re: RFC: Tutorial: use strict; now what!?" created="2012-02-08 17:03:22" updated="2012-02-08 17:03:22">
<type id="11">
note</type>
<author id="647953">
sundialsvc4</author>
<data>
<field name="doctext">
&lt;p&gt;
I agree with the sentiments expressed here, including the use (not mentioned) of &lt;tt&gt;use warnings&lt;/tt&gt;. &amp;nbsp; Basically, I think, the idea is to force as many dumb mistakes to be detected &amp;ldquo;at compile time&amp;rdquo; as possible. &amp;nbsp; When you are writing thousands of lines of code, little will typos creep in that you didtn recognize at the time. &amp;nbsp; And the time that you want to detect those isssues is, &lt;em&gt;right now.&lt;/em&gt; &amp;nbsp; The computer has the amazing ability to detect the slightest inconsistency, and you want the computer to be doing everything in its power to assist you in that regard. &amp;nbsp; It will never encounter &amp;ldquo;Paris in the the spring&amp;rdquo; without instantly flagging the extra &amp;ldquo;the.&amp;rdquo; &amp;nbsp; But did you, while reading this, encounter every one of the five tpyos I put in here? &amp;nbsp; (If your browser underlined them for you, it doesn&amp;rsquo;t count.)
&lt;/p&gt;&lt;p&gt;
If you find that you &lt;em&gt;must&lt;/em&gt; use a construct that flags a warning, you can use the &lt;tt&gt;no&lt;/tt&gt; construct, &lt;u&gt;and&lt;/u&gt; liberal and detailed comments, to explain exactly what you are masking-out and exactly why. &amp;nbsp; (You &lt;em&gt;will not&lt;/em&gt; remember, even with regard to your own code.) &amp;nbsp; Then turn the feature right back on as soon as possible.
&lt;/p&gt;</field>
<field name="root_node">
952446</field>
<field name="parent_node">
952446</field>
</data>
</node>
