in reply to Re^3: getting headers from essage
in thread getting headers from essage

> You're using a hash slice,

Worse, it's the new extended kind which returns key-value pairs, forgot the terminology for it °

DB<23> $hr= { To => [qw/a b c/] } DB<24> x %$hr{To} 0 'To' 1 ARRAY(0x55ef21ab6818) 0 'a' 1 'b' 2 'c' DB<25> x @$hr{To} # classic hash slice 0 ARRAY(0x55ef21ab6818) 0 'a' 1 'b' 2 'c' DB<26> x @{%$hr{To}} # only "works" with one hash key 0 'a' 1 'b' 2 'c'

update

interestingly even the documentation of this module is faulty

https://metacpan.org/dist/Mail-IMAPClient/view/lib/Mail/IMAPClient.pod#parse_headers

    "To"      => [ "Big Shot <big.shot@bigco.com> ] ,

(spot the missing " )

I think the OP should use Data::Dumper or Data::Dump to inspect the $hashref and isolate his problem.

Cheers Rolf
(addicted to the Perl Programming Language :)
see Wikisyntax for the Monastery

°) apparently key-value-slice since the "new" (cough) 5.20 ... wait... perldoc says Key/Value-Hash-Slice

Replies are listed 'Best First'.
Re^5: getting headers from essage
by ikegami (Patriarch) on Dec 16, 2025 at 20:50 UTC

    Yes, sorry, that's what I meant and clearly demonstrated.

      Sure, I just wanted to highlight why it looked so weird.

      But the question remains if Perl shouldn't better throw a warning if there's a list inside a dereference.

      I can't see any reason why not, except backwards compatibility to bad code which fails on warnings (convoluted case tho)

      Cheers Rolf
      (addicted to the Perl Programming Language :)
      see Wikisyntax for the Monastery