Documented behaviour. From perlfunc, the entry for map:

               "{" starts both hash references and blocks, so
               "map { ..." could be either the start of map BLOCK
               LIST or map EXPR, LIST. Because perl doesn't look
               ahead for the closing "}" it has to take a guess
               at which its dealing with based what it finds just
               after the "{". Usually it gets it right, but if it
               doesn't it won't realize something is wrong until
               it gets to the "}" and encounters the missing (or
               unexpected) comma. The syntax error will be
               reported close to the "}" but you'll need to
               change something near the "{" such as using a
               unary "+" to give perl some help:

                   %hash = map {  "\L$_", 1  } @array  # perl guesses EXPR.  wrong
                   %hash = map { +"\L$_", 1  } @array  # perl guesses BLOCK. right
                   %hash = map { ("\L$_", 1) } @array  # this also works
                   %hash = map {  lc($_), 1  } @array  # as does this.
                   %hash = map +( lc($_), 1 ), @array  # this is EXPR and works!

                   %hash = map  ( lc($_), 1 ), @array  # evaluates to (1, @array)

               or to force an anon hash constructor use "+{"

                  @hashes = map +{ lc($_), 1 }, @array # EXPR, so needs , at end

               and you get list of anonymous hashes each with
               only 1 entry.

amd from perltrap:

       o Parsing
           When perl sees "map {" (or "grep {"), it has to guess
           whether the "{" starts a BLOCK or a hash reference. If
           it guesses wrong, it will report a syntax error near
           the "}" and the missing (or unexpected) comma.

           Use unary "+" before "{" on a hash reference, and
           unary "+" applied to the first thing in a BLOCK (after
           "{"), for perl to guess right all the time. (See "map"
           in perlfunc.)

Abigail

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&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.