XML::Simple isn't. The immediate problem is a need to use ForceArray. However your code can stand a fair bit of tidying up generally. There is no need to use prototypes. You should avoid overloading identifiers (r used for the name of two different subs especially is nasty). Identifiers generally should indicate their purpose. Consider:

#!/usr/bin/perl
use warnings FATAL => qw(all);
use strict;
use Data::Dump qw(dump pp);
use XML::Simple qw(:strict);

run();

sub run {
    my $xml = XMLin(
        <<'END', ForceArray => ['parameters'], KeyAttr => ['declaratio
+n_name', 'name']);
  <classes name="Panoply::BAR">
    <public_methods>
      <members name="BAR" const="no" kind="function" protection="publi
+c"
        static="no" virtualness="non_virtual" volatile="no"
      >
        <parameters declaration_name="pciReg" type="Register::Ptr" />
      </members>
    </public_methods>
    <enums>
      <members name="ObjectState" kind="enum" protection="public" stat
+ic="no" virtualness="non_virtual">
        <values name="NEW">
        </values>
        <values name="REFRESHED">
        </values>
        <values name="DIRTY">
        </values>
      </members>
        </enums>
  </classes>
END
    my @list;
    my $sub = sub {push(@list, shift(@_) . ": " . join(" => ", @_))};

    findPath($sub, $xml, "pciReg");
    findPath($sub, $xml, "DIRTY");
    findPath($sub, $xml, "parameters");
    print join("\n", @list), "\n";
}


sub findPath {
    my ($sub, $xmlFrag, $match, @path) = @_;

    return unless $xmlFrag;

    if (ref($xmlFrag) =~ /HASH/) {
        for my $key (sort keys %$xmlFrag) {
            if ($key !~ /$match/) {
                findPath($sub, $xmlFrag->{$key}, $match, @path, $key);
            } else {
                $sub->($match, @path);
            }
        }
    } elsif (ref($xmlFrag) =~ /ARRAY/) {
        for my $fragIdx (0 .. $#$xmlFrag) {
            unless ($xmlFrag->[$fragIdx] =~ /$match/) {
                findPath($sub, $xmlFrag->[$fragIdx], $match, @path,
                    $fragIdx + 1);
            } else {
                $sub->($match, @path);
            }
        }
    }

    return;
}

[download]

Prints:

pciReg: public_methods => members => parameters
DIRTY: enums => members => values
parameters: public_methods => members

[download]
True laziness is hard work

In reply to Re: sub that finds ancestor elements by GrandFather
in thread sub that finds ancestor elements by jccunning

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.