much of the code in the Scriptome would make an excellent tutorial on Perl one-liners
I would not be so quick about excellence.
Take for example, this page
perl -ne 'BEGIN {$col=1}' -e 's/\r?\n//; @F=split /\t/, $_; $sum += $F
+[$col];
END {warn "Sum of column $col for $. lines\n"; print "$sum\n"}' file.t
+ab
I see an inefficient replacement of newline, instead of chomp. But since
this is a one-liner, the "-l" option will do instead, and it will also
save the output newlines.
Then, the @F=split /\t/, $_; could be easily replaced
by the "-a" autosplit option, which will happily take charge of different
whitespace types, other than tabs.
I would say that this one-liner woult be better written as
perl -e 'BEGIN {$col=1}' -lane '$sum += $F[$col];
END {print "Sum of column $col for $. line: $sum"}' file.tab
Or, I should even dare this:
perl -lane '$sum += $F[1]; END {print $sum}' file.tab
It's shorter, thus easier to write, and less mistakes to make
when copying it.
-
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.