Uhm, yes. That's the point of a map, isn't? And perhaps you haven't realized it, all foreach blocks are evaluated for each element of the list as well.

I'm referring to how map takes the result, the final statement, of each block and passes it on to the resulting list. Judging by your next statement, you understood perfectly what I was saying but still choose to be smartass anyway:

Yeah, neat, isn't? That's the point of map, you know.

But I understand what you are saying. It's utterly unclear to write a map this way. After all, it's also unclear to return a result from a subroutine; it's much clearer if the subroutine explicitly assigns the return value to a variable. All well written programs do.

Nice contrived example to try to prove your point. The subroutine equivalent would be leaving off the return statement and letting the last statement implicitly be the return value:

sub ringForward {
    ...

    $modem->send($tone, $duration);
}

sub ringForward {
    ...

    return $modem->send($tone, $duration);
}

[download]

But I guess one is just as clear as the other, right? You can easily tell whether or not you can check the return value just from looking at either one, right?

In reply to Re^7: "advanced" Perl functions and maintainability by William G. Davis
in thread "advanced" Perl functions and maintainability by geektron

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.