I am writing an object-oriented Perl application with 30 to 40 classes.

My cohort and I have been having heated discussions about the implementation and behavior of the error handling and logging of the application.

Essentially we are looking for the best practices to accomplish this in an object-oriented Perl application.

Thus far we have a logging class that is inherited by classes that want to log. The logging class has class data that we initialize immediately on starting the application. However, as we work through the design, it appears that the logging class and error handling can share some of the same work.

Can you point out some best practices for the implementation of error handling and logging.

Thanks, hackdaddy

In reply to Error Handling and Logging for Object-Oriented Perl Application by hackdaddy

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.