Downsides are that it looks ugly if you don't have an __DIE__ handler
If you overload the stringification operator for your object then you should be able to get the desired behaviour for die.

Another option is that you could overload die and warn e.g

BEGIN { *CORE::GLOBAL::die = sub { CORE::die("$_[0]->{type}: $_[0]->{msg}\n"); }; *CORE::GLOBAL::warn = sub { CORE::warn("$_[0]->{type}: $_[0]->{msg}\n"); }; } warn { type => "warntest", msg => "missing point" }; die { type => "dietest", msg => "and I'm done" }; __output__ warntest: missing point dietest: and I'm done
Extraordinarily hackish, but at least there's an option :)
HTH

_________
broquaint


In reply to Re: Re: Re: Argument stringification in __WARN__ and __DIE__ by broquaint
in thread Argument stringification in __WARN__ and __DIE__ by Rhandom

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.