I start any file based programs with strict and warnings. But I rarely -Mstrict with -e. Often that means that when a -e program begins to grow to the point that my shell's (bash or cmd.exe depending on platform) readline is more cumbersome than moving the code into a file and bouncing to a shell to execute (or keybinding to execute for editors that handle it well) I move it to a file, usualy adding strict and warnings before I even copy the code from the command line, and then forgetting before the first time I run the file that I still need a few my's sprinkled around.
I'm fairly good at judging before hand what will be a one off with maybe an edit or two and a program that will require editing and debugging, but ever couple of months I'm not so lucky.
Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
Want more info? How to link or
or How to display code and escape characters
are good places to start.