What are you hoping to achieve with CustumErrorObj.pm (many would spell that "Custom..." btw) that you don't get with Error.pm in terms of inheritance?

You seem to be saying that you don't want your mailer/viewer/logger classes deriving from a common base class. It's not clear to me how you can avoid that unless what you really intend is to add an Error.pm like interface to each class independently. On the basis of the "If it walks like a duck and barks like a duck, it is a duck", you could add the appropriate members to each class and they will look to any interested code as though they are the appropriate sort of duck.

(See the threads Re: isa() on any scalar, Is "ref $date eq 'ARRAY'" wrong? and Re^2: RFC: Object::Proxy (or somesuch) for relevant ideas.)

DWIM is Perl's answer to Gödel

In reply to Re: Error and objects: general Q by GrandFather
in thread Error and objects: general Q by Discipulus

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.