You should keep in mind that a name *::Lite would look very appealing to many programmers who already have to include lots of module monsters into their code.

If your module just seems to differ in the details from the other modules you might as well just take a nondescriptive name. Rose::DB or Moose got used for their merits and not for a catchy name after all.

But the overall impression I get from your module description is that its output is just more informative than all the other Exception modules, so how about

Exception::Descriptive

Exception::Informative

Exception::Clear

Exception::More

And I, for one, welcome our new exception overlord ;-)

In reply to Re: RFC: A better name for an exception handling module? by jethro
in thread RFC: A better name for an exception handling module? by ELISHEVA

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.