comment on

1. Is there some nuance in the code i'm missing that will make it be short and readable instead of adding ugly hacks to get map to read that as a code block instead of a hash reference?

The easiest/cleanest way seems to be to add parens around the contents... $two->( map { (anda => $_) } @one );.

2. Is anyone else having this problem? Or is it just me?

Your code broke for me as well

3. Assuming it's standard behavior from 5.6.1, is it fixed in 5.8?

I get the same results from 5.8.0.

We're not surrounded, we're in a target-rich environment!

In reply to Re: (5.6.1) map mayhem? by jasonk
in thread (5.6.1) map mayhem? by jynx

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.


P is for Practical
	PerlMonks