Tested variants that don't need @data: 

print "@$_\n" foreach sort {
  $a->[0] <=> $b->[0] or
  $a->[1] cmp $b->[1] or
  $a->[2] cmp $b->[2]
} map {
  my ($s,$v)=@$_;
  map {[$v->{$_}, $s, $_]} keys %$v;
} map {
 [$_,$hash->{$_}]
} keys %$hash;

[download]
print "@$_\n" foreach sort {
  $a->[0] <=> $b->[0] or
  $a->[1] cmp $b->[1] or
  $a->[2] cmp $b->[2]
} map {
  my $s = $_;
  map { [ $hash->{$s}{$_}, $s, $_] } keys %{$hash->{$s}}
} keys %$hash;

[download]

I would definitely use a secondary data structure like @data. As a wise man once said,

"Always code as if the guy who ends up maintaining your code will be a violent psychopath who knows where you live."

In reply to Re: Hash sorting by Util
in thread Hash sorting by artist

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.