Fixed the code

 %new_db = (1 , 'gedit-2.2.2-i386-1.tgz',
             2 , 'ppp-3.4.1-i386-2.tgz');



new_packages($fcount,\%new_db);

sub new_packages {
    my %packages =%{ $_[1]};
    print "Found $_[0] packages for download: $_\n" if ($fcount > 1);
    print "Found $_[0] package for download: $_\n" if ($fcount == 1);
    print "Which one would you like to install?:\n";
    foreach my $key (keys (%packages)) {
        print "$key) $packages{$key} \n"
    }
}

[download]

Note that I changed your passing of the hash to passing of a reference to the hash and I de-reference it in the sub.

Otherwise it is just going to look like an array of scalars.

Peter L. BergholdBrewer of Belgian Ales
Peter@Berghold.Netwww.berghold.net
Unix Professional

In reply to Re: parse hash to sub by blue_cowdawg
in thread parse hash to sub by atnonis

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.