I don't know if you have updated yourself about PATH, so here is one way: put /usr/local/bin as the first entry in PATH system-wide, such as PATH=/usr/local/bin:$PATH. It's simpler and non-destructive (no file renameing).But it's not 100%-success-guaranteed either. Some programs insist to explicitly set their PATHs to certain entries and specific order.

Anyhow, the idea of forcing everything to use the new Perl installation is just fine since Perl is backward compatible. Specially, new 5.10 features must be turned on explicitly so nothing shold be broken by this alone. The only issue left is about the non-core Perl modules installed from CPAN. Both versions hold different idea about where to lookup the modules due to different @INC entries. If you never installed CPAN modules before (even if you didn't realize), you're probably safe. If you really never install modules from CPAN, well, start doing it. It's easy, and fun too :-)

Now about the script. I second Tanktalus that there's nothing wrong with $_, specially in grep and map blocks, as well as in simple for construct. I even perceive that grep and map would lose their touch without $_, not that they'd lose their functionalities at all. It's not only about convenience and short code, it's also about aliasing (regardless of whether or not it is a feature; it is for me).

I find myself hard to use your rating scale as well, as "retarted" can be at either end of the scale. But let me say, it's a good start, go for it, and get hunger for more.

---

---

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