I am a little late to the party here, and as a fairly new perl programmer myself, there have been a lot of times where after reading the documentation for a given perl module I have had to do pretty exhaustive searches to find anything that gave me even a beginning of a clue as to how to do something.

Oftentimes this is because the docs are written for people that are more familiar with perl than I am, or there is a very simple example and it can do "all these other things" but they seem to have no good docs. Why that is, I dunno, it could be that I just don't know what I am looking for, or where to look.

My reason for replying is that there are many things that I am learning on my own, but I often see that I have written some chunk of code and after looking at it I think "Damn, there must be a far better way to do that. I don't particularly want someone to write the code for me, but I wonder sometimes if it would be better if someone that was far better with perl than I took the time to provide the code and then subsequently explain it.

I have found some code snippets on the web that do what I need, and they are very short which is nice other than, while I understand that it works for what I am using it for, I would rather see the 10 lines of code that were smashed down into that fancy one-liner I am now using and I would like to see them explained and a what,why,where,when,how given about why the one-liner works and how it all relates, so some theory I guess.

Just my $.02, but I think examples by experienced folks come in handy. On top of that, the more examples I see or are available, the less questions I generally need to ask :)

Right now I am questioning what I wrote because I am pretty sure that was long-winded and didn't actually cover what I wanted to, but my brain hurts, so I am not bothering to edit it or anything. Deal :)

---

---

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