<?xml version="1.0" encoding="windows-1252"?>
<node id="1011814" title="Re^6: The Most Essential Perl Development Tools Today" created="2013-01-05 18:29:08" updated="2013-01-05 18:29:08">
<type id="11">
note</type>
<author id="757127">
tobyink</author>
<data>
<field name="doctext">
&lt;p&gt;While I mostly agree with this there is one use case for P::C that hasn't been mentioned yet, but I can see the potential benefit.&lt;/p&gt;

&lt;p&gt;Let's assume that I &lt;em&gt;always&lt;/em&gt; use the two argument &lt;c&gt;open&lt;/c&gt;. But that a few days ago, I made a new year's resolution to embrace three argument &lt;c&gt;open&lt;/c&gt; as a matter of personal preference. I could use P::C with a highly stripped down configuration to remind myself not to use two argument &lt;c&gt;open&lt;/c&gt; on all my code for the next couple of months until muscle memory takes over.&lt;/p&gt;

&lt;p&gt;So the use case is: reminding yourself about style guidelines that you have decided to follow, yet sometimes forget through laziness or force of habit. After a little while you probably start doing it automatically and can then abandon P::C. Or you don't, and decide to go back to your old way.&lt;/p&gt;

&lt;!-- Node text goes above. Div tags should contain sig only --&gt;
&lt;div class="pmsig"&gt;&lt;div class="pmsig-757127"&gt;
&lt;small&gt;&lt;small&gt;
&lt;tt&gt;perl -E'sub Monkey::do{say$_,for@_,do{($monkey=&amp;#x5B;caller(0)]-&gt;&amp;#x5B;3])=~s{::}{ }and$monkey}}"Monkey say"-&gt;Monkey::do'
&lt;/tt&gt;&lt;/small&gt;&lt;/small&gt;
&lt;/div&gt;&lt;/div&gt;</field>
<field name="root_node">
1011175</field>
<field name="parent_node">
1011684</field>
</data>
</node>
