I might be so bold as to suggest that a model for "native Perl" would be the code written by those of us that have spoken Perl the most frequently and the longest (and more importantly, have written it enough different ways that we've had time to compare which ones really suck on a reading three months later).

However, one should also consider that part of the coolness of Perl is having so many ways to do things. Certainly, using a for loop instead of a foreach loop to process every element of an array is "less Perlish", but would something like the Schwartzian Transform, which is basically a Lisp-technique adapted to Perl, be "native Perl"? It's hard to tell.

If you can say in three nice simple lines what someone else said in six, I'd say the three lines are probably more Perlish. But when you start trading three lines for three lines, I'm not sure there's a gain. But it's not all about lines of code... that's just my first rule of thumb.

-- Randal L. Schwartz, Perl hacker
Be sure to read my standard disclaimer if this is a reply.

---

---

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