Yeah sorry I missed that requirement.
The OP wasn't really a SSCCE tho. Duplicated keys would have shown the problem. :)
Personally I would go for a clear 2 line approach, all this dereferencing doesn't make it more readable.
Or to repeat my old mantra:
- Perl would be better of with autobox-methods¹
{%A, %Z}->keys
On a side note: I always have the feeling that a big deal of perl4's appeal got lost with my, because of conceptual problems.
Hmm...People will misunderstand this.
What I mean is that many things are elegantly solved if you don't need 'my'. A language design problem.
¹) compare autobox
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.