Thanks!
I hadn't thought of #2 (things you didn't like).
I had a foreach when I was using a hash to store
data, but switched to the C-style for when I made
the move to an array because, well just because that's the
other idiom I'm familiar with. Although, while your suggestion
is pretty safe for the chars loop isn't there a larger
potential with the lines loop of instantiating a large list?
As for #1, I know I know, but at least I didn't go with
-s! (I was tempted but especially didn't want to
force use of = to pass a value.) That and it's such a simple
thing, I most certainly would have used Getopt::*
if it was any more complicated; two arguments, arguments
with optional values, or arguments with types. Yeah, it
actually works without fully qualified $a and
$b (had like that for awhile) but figured I'd go
for the gusto.
Thanks again.
--
perl -p -e "s/(?:\w);([st])/'\$1/mg"
-
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>
<u> <ul>
-
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
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
