The only way this (my) code can throw a division by zero error is when you tell the program to read an empty data file. This can be mitigated. 
sub average_hourly_wage{
    my $self = shift;
    my $wages = 0; my $count = 0;
    
    foreach my $employee ( @{ $self->{EmployeeList} })
    {
        $wages += $employee->{hourlywage}; $count++;
    }
    
    return $count ? $wages / $count : 0;
}

[download]
And of course, if the data file is empty, there is nothing in the Employee-List, thus ->find returns undef. That however, is something you have to deal with in the calling code. 
if ( my $e = $EmployeeList->find("holli") )
{
    print $e->pay, "\n";
} 
else
{
    print "User not found\n";
}

[download]


holli

You can lead your users to water, but alas, you cannot drown them.

In reply to Re^5: Newbie question under time constraint by holli
in thread Newbie question under time constraint by crazedrat

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.