Two notes:
  1. sort can take a subname, so a simple sort netFetObj::fetSort @list looks cleaner than your construct.
  2. if you don't use a prototyped sort sub, $a and $b are globals in package something_else. That means you should refer to them as $something_else::a and $something_else::b inside fetSort.
To summarize: 
package netFetObj;
sub fetSort {
print " ######### A = $something_else::a \n";
print " ######### B = $something_else::b \n";
    my $ftA = $something_else::a->{"fet"};
    my $ftB = $something_else::b->{"fet"};
    $fetType->{$ftA} <=> $fetType->{$ftB}
}

  
package something_else;
    foreach my $fetOBJ ( sort netFetObj::fetSort @{ $OBJ->{"fets"} } )
+ {
        buildFet($FH,$fetOBJ,$OPT);
    }

[download]

In reply to Re: sorting objects by rhesa
in thread sorting objects by Anonymous Monk

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.