I agree with the comments about the redundant map. As for readability, I'm a big fan of judicious placement of carriage returns. When it comes to Perl's pipeline idioms, each map or grep is another step in the pipeline. That produces code like the following. I've left the redundant map in to highlight the effect.

    return
        map { split(/ /, $_, 2) }
        map { uc($_) }
        @somearray
[download]

Sure, if the reader is very new to Perl, they don't understand pipeline idioms at all. However, if the idiom is formatted as consistently as possible, they can absorb it just as quickly as the chaining-return idioms of other languages, like joe = foo().bar().baz().

---

---

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