in reply to Turning foreach into map?

There are two syntaxes for calling map. If you are passing a block of code, there is no comma between the block and the list. If you are passing an expression, there is a comma. In this case, since it's just a string, I'd recommend the expression form.

Watch out if your expression is surrounded by parentheses, though, because map will think they enclose all of its arguments. You either need two sets of parens (one around your expression, and one around all of map's args), or you don't need any. In your case, you don't need any. 

return map "$url/$_\n", @list;

[download]
Caution: Contents may have been coded under pressure.

Replies are listed 'Best First'.
Re^2: Turning foreach into map?
by tlm (Prior) on Apr 04, 2005 at 21:18 UTC

    Watch out if your expression is surrounded by parentheses, though, because map will think they enclose all of its arguments. You either need two sets of parens (one around your expression, and one around all of map's args), or you don't need any.

    You can also get away with the single set of parens if you disambiguate it with +: 

    @out = map +( ... ), @in;

    [download]
    I find myself using this trick all over the place, not only with map and grep but with, e.g. print: 
    print +( $foo ? $bar : $baz ) . $quux;

    [download]
    Without the + above, the last expression would result in the printing of only the value of the expression in the parens. (Although, if warnings are on, perl will say something about interpreting print (...) as a function.)

    the lowliest monk

[reply]
[d/l]
[select]

In Section Seekers of Perl Wisdom