To be honest I rarely find myself doing a "pure perl" one liner more sophisticated than the occasional perl -pi -e's/something/somethingelse/g' *, however every once in a while something a little more complicated comes up and you know you've got to use different bits of the toolkit:

perl -MEmail::Folder -e'print $_,"\n" foreach sort map { $_->header("F
+rom")} Email::Folder->new("mail/london_pm")->messages()' | uniq -c | 
+sort -n
[download]

Now I'm sure you could do this entirely as purely perl, but what would be the point (apart from proving that you can do it)? As it is the entire pipeline could be made shorter by piping through an additional sort before the uniq rather sorting in Perl (you can lose the map as well as the sort then). This is after all the point of having pipelines and filters and having a rich toolset.

/J\

---

---

• 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.