The "keywords" method seems to be coded to ignore the parameter, causing the behaviour you see:
sub keywords { my $self = shift; croak 'Not called as a method by parent object' unless ref $self && UNIVERSAL::isa($self, __PACKAGE__); my %keywords; my $stor = $objstore->{_refaddr($self)}; for my $handle (@{$stor->{parsed}->{handles}}) { for my $keyword ($handle->keywords) { $keywords{$keyword} = 1; } } return sort(keys(%keywords)); }
Since the documentation is not explicit about what it SHOULD do, it is not technically a bug. But I would call it a poor example.

I would recommend sub-classing it to do what you ned, and try to contact the author.

     Potentia vobiscum ! (Si hoc legere scis nimium eruditionis habes)


In reply to Re: parse dmidecode keywords by NetWallah
in thread parse dmidecode keywords by perldesire

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • 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:
    & &amp;
    < &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.